From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MxqhI-0001gP-HH for garchives@archives.gentoo.org; Tue, 13 Oct 2009 23:22:28 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CC28AE0772; Tue, 13 Oct 2009 23:22:26 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id A4940E0772 for ; Tue, 13 Oct 2009 23:22:26 +0000 (UTC) Received: from angelstorm (cpe-66-75-3-21.san.res.rr.com [66.75.3.21]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id EFB2EB4D6E for ; Tue, 13 Oct 2009 23:22:25 +0000 (UTC) Date: Tue, 13 Oct 2009 16:22:20 -0700 From: Joshua Saddler To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] openrc-0.5.1 arrived in the tree Message-ID: <20091013162220.5aa80a54@angelstorm> In-Reply-To: <200910140052.06682.cla@gentoo.org> References: <200910091957.09193.zzam@gentoo.org> <200910131815.52307.vapier@gentoo.org> <4AD51E4F.1090105@avtomatika.com> <200910140052.06682.cla@gentoo.org> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.6; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/4j2d0RZtrntjYk4UU50=k0q"; protocol="application/pgp-signature" X-Archives-Salt: 099f68c4-a9b3-4203-9f7e-68a3ea6ad551 X-Archives-Hash: 099a84b2d05b47123d908073bc04070c --Sig_/4j2d0RZtrntjYk4UU50=k0q Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Wed, 14 Oct 2009 00:52:06 +0200 Dawid W=C4=99gli=C5=84ski wrote: > Upstream already provides such a documentation as you can see above. Gent= oo=20 > provides migration guide. I believe doc team will update use flag descrip= tion=20 > as soon as it's possible. In this case, "As soon as it's possible" means "when someone sends a patch = to bugzilla, because I don't know what the hell to do." And I'm the documen= t maintainer. Take a look at the forums, folks -- there are a *lot* of threads on this ma= jor change. Things that should be simple and straightforward, are not reall= y straightforward. Like the USE flag and reading its description in metadat= a.xml, or enabling it to get a working system. Right now, most of the repor= ts are from users who for one reason or another don't have the flag enabled= . And there are other regression reports from the .5 series in general, not= specific to the USE flag. And lots of users just don't know what this chan= ge brings, or what they should expect, or what they need from the new versi= on. Who'll help them out? Who holds the hands of these users, to tell 'em there= 's a migration guide with the fixes for these problems? Who writes the info= rmation in the guide so that it will be there when they need help? Not me. I don't write that stuff down. I'm "just" the guy who commits it. A= nd I've got nothing to help our users. So if you know how OpenRC 0.5.x is s= upposed to behave, from the perspective of a stable user moving to ~arch Op= enRC . . . then for the love of our users, go to bugs.gentoo.org and get me= some patches. --Sig_/4j2d0RZtrntjYk4UU50=k0q Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEARECAAYFAkrVC68ACgkQxPWMzpKk6kMsaACePPG0BFOfGBG21gct+Kmvr3Vp q7QAn07AZQXipZfku5Ln29qsaN/8kADE =JGgh -----END PGP SIGNATURE----- --Sig_/4j2d0RZtrntjYk4UU50=k0q--