From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JVOMG-0004cg-31 for garchives@archives.gentoo.org; Sat, 01 Mar 2008 09:50:20 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DF004E006D; Sat, 1 Mar 2008 09:50:17 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 93752E006D for ; Sat, 1 Mar 2008 09:50:17 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 2CFB464DA0 for ; Sat, 1 Mar 2008 09:50:17 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -2.064 X-Spam-Level: X-Spam-Status: No, score=-2.064 required=5.5 tests=[AWL=0.535, BAYES_00=-2.599] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f22V5dbgokcV for ; Sat, 1 Mar 2008 09:50:11 +0000 (UTC) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id D0F2D669EE for ; Sat, 1 Mar 2008 09:50:09 +0000 (UTC) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1JVOM0-0008Pu-Fl for gentoo-dev@gentoo.org; Sat, 01 Mar 2008 09:50:04 +0000 Received: from ip68-231-12-179.ph.ph.cox.net ([68.231.12.179]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 01 Mar 2008 09:50:04 +0000 Received: from 1i5t5.duncan by ip68-231-12-179.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 01 Mar 2008 09:50:04 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-dev] Re: Baselayout-2 progress? Date: Sat, 1 Mar 2008 09:49:57 +0000 (UTC) Message-ID: References: <47C812CF.2020903@wildgooses.com> <47C82C9F.7040701@gentoo.org> <47C82FB7.9030308@wildgooses.com> <200802291707.17936.roy@marples.name> <47C8E29A.2020003@gentoo.org> 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: text/plain; charset=UTF-8 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-12-179.ph.ph.cox.net User-Agent: Pan/0.132 (Waxed in Black) Sender: news Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 105f6472-afa7-46dd-8612-d40b83821744 X-Archives-Hash: 4c29c13edabf3d72b2d648ffbd4ca07f Doug Klima posted 47C8E29A.2020003@gentoo.org, excerpted below, on Fri, 29 Feb 2008 23:59:06 -0500: >> Is direct upgrade from previous baselayout-2.0.0-rcX going to be >> supported? I was running that for some time and just now added and >> upgraded to the via layman version. There's a blocker, of course, as >> openrc is now providing most of the files that baselayout did. >=20 > You just answered your own question. If another package now provides > files that an existing package provides, they must be blockers. Thus the "of course"... > Considering baselayout-2.0.0_rcX was a masked version and never > recommended, it's also not in the direct upgrade path. The proper > upgrade is what you've detailed out below. Such are the risks when you > unmask a package and install it on your machine. Which is why I'm not particularly complaining, just asking. Practically speaking, while it's not required by any means, some devs=20 choose to acknowledge the symbiotic relationship between pre-release=20 testers willing to take that risk and do the work to find and file bugs,=20 thus helping to make the general release far less buggy, and the devs who= =20 depend on such testers for that function. The testers do a favor for the= =20 devs with all that early testing and bug filing (sometimes with patches),= =20 and many devs choose to return it by providing a working upgrade path=20 from the pre-releases to the general release. Among other things, it=20 makes for happier testers, who are then likely to be repeat testers, the=20 next time an upgrade comes along. It's also worth mentioning that a call for testers went out, so it's not=20 as if those that answered it, particularly if the DID actively look for=20 and file bugs as they found them, were doing it entirely of their own=20 accord. Again, it's doing the developer a favor, so it's a nice gesture=20 if the developer chooses to return the favor by smoothing the upgrade=20 path. Not something he has to do, but something he /can/ do, to increase= =20 the chances of folks who already know the process again taking him up on=20 the invitation, the next time he needs something tested. =3D8^) So anyway, I thought it was worth asking about, in case it had slipped=20 his mind or he hadn't thought of it. No big deal either way, but it'd be= =20 a nice gesture if it's not too difficult to setup. --=20 Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman --=20 gentoo-dev@lists.gentoo.org mailing list