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 1JHMkp-0004qx-SF for garchives@archives.gentoo.org; Tue, 22 Jan 2008 17:17:44 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B1B0CE0B0F; Tue, 22 Jan 2008 17:17:24 +0000 (UTC) Received: from vms173003pub.verizon.net (vms173003pub.verizon.net [206.46.173.3]) by pigeon.gentoo.org (Postfix) with ESMTP id 95DBFE0B0F for ; Tue, 22 Jan 2008 17:17:24 +0000 (UTC) Received: from gw.thefreemanclan.net ([71.242.210.100]) by vms173003.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JV200MTP2D30CB0@vms173003.mailsrvcs.net> for gentoo-project@lists.gentoo.org; Tue, 22 Jan 2008 11:10:16 -0600 (CST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by gw.thefreemanclan.net (Postfix) with ESMTP id E2D4512418C; Tue, 22 Jan 2008 12:13:01 -0500 (EST) Date: Tue, 22 Jan 2008 12:13:00 -0500 From: Richard Freeman Subject: Re: [gentoo-project] Re: Plan, then communicate In-reply-to: <20080122044540.GA11340@redwoodscientific.com> To: John Lawles Cc: Alec Warner , gentoo-project@lists.gentoo.org Message-id: <4796241C.7000409@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Project discussion list X-BeenThere: gentoo-project@lists.gentoo.org MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit References: <20080120215706.GA16357@redwoodscientific.com> <20080120233809.GA18052@redwoodscientific.com> <200801201908.07265.vapier@gentoo.org> <20080121015439.GA18636@redwoodscientific.com> <20080121193103.GA29429@redwoodscientific.com> <4795580D.9090602@gentoo.org> <20080122044540.GA11340@redwoodscientific.com> User-Agent: Thunderbird 2.0.0.9 (X11/20071116) X-Archives-Salt: 6924231b-1ebc-4bbd-a89a-eca6d7513837 X-Archives-Hash: 20daa72b70c2ee06cb22410c02cf1122 John Lawles wrote: > > The concept is that there would be a separate team maintaining > the stable tree. A precedent for this would be the Linux kernel's > two-track development. > Actually, in theory that is what already happens with stable keywording - or is supposed to happen. It is a different group of developers who maintain the stable tree (well, there is overlap, but some people wear multiple hats). Expat was a real mess - mainly because they break ABI and it doesn't use slotting. I'm not sure why slotting couldn't have been used in this case (others might be able to comment on this). What we need is a better mechanism of warning users that they're about to do something that could cause them major headaches. ELOG is useless when you find out after the fact. revdep-rebuild working better would also be nice. If it won't work the ebuild should abort prior to install with a link to a document indicating what will need to be done, and then users can read and understand it before they break things. > As a mere end-user, I am not recommending any particular > solution. I am suggesting that more effort be devoted to > (a) recognizing user frustrations, (b) proposing good solutions, > and (c) letting us know that you see the problems and that > solutions are being worked on. > I agree that this is something that does need better attention in general. I find it a bit frustrating to have to carefully check my emerge -auD lists to ensure that the whole system won't blow up after the install - and prior to last Aug I'd never even heard of expat... -- gentoo-project@lists.gentoo.org mailing list