From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8817 invoked from network); 11 Aug 2004 12:21:50 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 11 Aug 2004 12:21:50 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1Bus72-0002LP-UH for arch-gentoo-dev@lists.gentoo.org; Wed, 11 Aug 2004 12:21:49 +0000 Received: (qmail 14633 invoked by uid 89); 11 Aug 2004 12:21:48 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 28243 invoked from network); 11 Aug 2004 12:21:48 +0000 From: Chris Bainbridge Organization: Gentoo Foundation To: gentoo-dev@lists.gentoo.org Date: Wed, 11 Aug 2004 13:21:45 +0100 User-Agent: KMail/1.6.2 References: <20040808185144.GB29077@mail.lieber.org> <200408102119.26115.chrb@gentoo.org> <20040811052119.4e0cb049@andy.genone.homeip.net> In-Reply-To: <20040811052119.4e0cb049@andy.genone.homeip.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408111321.46084.chrb@gentoo.org> X-OriginalArrivalTime: 11 Aug 2004 12:22:05.0170 (UTC) FILETIME=[D0220520:01C47F9D] Subject: Re: [gentoo-dev] GLEP 19, reloaded (again) X-Archives-Salt: b2d6771c-3c10-41cc-b6bb-56d163811b87 X-Archives-Hash: 1390ce29f92d51fd33e71fbb729553e9 On Wednesday 11 August 2004 04:21, Marius Mauch wrote: > In that case you can just use Redhat instead. There is no point in > customizing our tree to behave like a Redhat release (e.g. what do you > do about baselayout, the initsystem, the new webapp-config, ...). > This would create a lot of work for us for (IMO) no benefit at all. The main point is reuse of manpower. Compatibility with commercial software is a secondary benefit. Behaving identically is not desirable or practical. My main concern is practicality. It isn't much work to create a list of essential package versions from another distros stable release and pin them in a frozen gentoo release. It is a lot of work to maintain a frozen tree that we create ourselves from scratch; please don't underestimate this! Everyone is discussing the technicalities of implementing a frozen tree, when we should be discussing whether its logistically possible. Questions: How many developers are willing to support a new frozen tree every 6 months for their packages? After 12 months you have 3 frozen trees, as well as the main portage tree to support. There are over 7000 open bugs on bugzilla with the existing tree! How are we going to manage and respond to bug reports from all of these frozen tree releases? -- gentoo-dev@gentoo.org mailing list