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 1L25tg-0007Z1-A2 for garchives@archives.gentoo.org; Mon, 17 Nov 2008 15:20:16 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C459FE027A; Mon, 17 Nov 2008 15:19:48 +0000 (UTC) Received: from apollo.fprintf.net (apollo.fprintf.net [208.75.87.34]) by pigeon.gentoo.org (Postfix) with ESMTP id 9BE6CE027A for ; Mon, 17 Nov 2008 15:19:48 +0000 (UTC) Received: (qmail 4729 invoked from network); 17 Nov 2008 15:19:46 -0000 Received: from unknown (HELO ?10.68.253.67?) (dang@fprintf.net@69.198.118.194) by apollo.fprintf.net with ESMTPA; 17 Nov 2008 15:19:46 -0000 Subject: Re: [gentoo-dev] Re: Proposal for how to handle stable ebuilds From: Daniel Gryniewicz To: gentoo-dev@lists.gentoo.org In-Reply-To: <20081116183814.0931c9de@halo.dirtyepic.sk.ca> References: <20081110181334.GD7038@aerie.halcy0n.com> <20081116183814.0931c9de@halo.dirtyepic.sk.ca> Content-Type: text/plain Date: Mon, 17 Nov 2008 10:10:57 -0500 Message-Id: <1226934657.4891.21.camel@athena.ghs.com> 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 X-Mailer: Evolution 2.24.1.1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 6b9aaea1-c70b-44c8-b06f-c1d38746c928 X-Archives-Hash: 6a91d0d900137823e1348a3861242e86 On Sun, 2008-11-16 at 18:38 -0600, Ryan Hill wrote: > The maintainer MUST NOT NEVER EVER NOT EVEN A LITTLE BIT remove the > latest stable ebuild of an arch without the approval of the arch team or > he/she will be fed to the Galrog. As long as the maintainer can pass off the maintenance of the (sometimes dozens) of ancient ebuilds that need to be kept around for that one arch to the arch team, and re-assign any resulting bugs to them, fine. Or, alternatively, unilaterally decide to drop all keywords for the arch in question. Yes, that was extreme, but no more than the previous quoted statement. There needs to be give and take here. Yes, it's really bad to remove the last stable ebuild for an arch. However, its *also* bad to have to maintain years old versions of lots of ebuilds. And yes, it will be a lot, since most packages don't exist in a vacuum, and require older deps (which possibly will be maintained by other maintainers than the first package, causing a cascade of old packages in the tree). All this will do in practice is cause maintainers to ignore bugs for those old packages for those few arches, since the maintainer won't have that version installed. In fact, in my experience, they frequently *can't* have that version installed, since it requires older versions of other packages that need to be upgraded to maintain newer versions of the same package. How much bit rot do we want in the tree? Daniel (who is both an arch team member and gnome team lead)