From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16016 invoked from network); 30 Apr 2004 15:18:26 +0000 Received: from smtp.gentoo.org (128.193.0.39) by eagle.gentoo.oregonstate.edu with DES-CBC3-SHA encrypted SMTP; 30 Apr 2004 15:18:26 +0000 Received: from lists.gentoo.org ([128.193.0.34] helo=eagle.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.24) id 1BJZmS-00053I-Uw for arch-gentoo-releng@lists.gentoo.org; Fri, 30 Apr 2004 15:18:24 +0000 Received: (qmail 29680 invoked by uid 50004); 30 Apr 2004 15:18:24 +0000 Mailing-List: contact gentoo-releng-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail Reply-To: gentoo-releng@lists.gentoo.org X-BeenThere: gentoo-releng@gentoo.org Received: (qmail 27384 invoked from network); 30 Apr 2004 15:18:24 +0000 From: Nathaniel McCallum To: gentoo-releng@lists.gentoo.org In-Reply-To: <200404301632.27101.pauldv@gentoo.org> References: <20040429132634.4AADB283B6@meep.gentoo.org> <200404301632.27101.pauldv@gentoo.org> Content-Type: text/plain Message-Id: <1083338210.8082.27.camel@aquinas.natemccallum.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.5.7 Date: Fri, 30 Apr 2004 11:16:50 -0400 Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-releng] Gentoo 2004.1 Release X-Archives-Salt: a3f20c60-3f54-4caa-8ac6-7b05c159dad3 X-Archives-Hash: 5bf273306c3a6c971bc7766cfed55802 On Fri, 2004-04-30 at 16:32 +0200, Paul de Vrieze wrote: > For me, this could best be implemented outside the gentoo project. We could > then list binary distro's based of gentoo or something like that. We then > need to add support for better binary dependency checking to portage, but it > should be possible to pull it off. Full continuously updatable like debian is > hard though and much of that work should be done by the developers of such a > gentoo based distro. I think it could be implimented in Gentoo, however, the first thing that needs to happen is frozen trees with only security updates. This is of great desireability for our enterprise users. Once that is done, adding binary support to that frozen tree is fairly easy. For instance, lets say we have a new frozen tree with every release. So right now the newest tree would be 2004.1. We could start by offering just the grp packages (and their security updates). A person can always move up trees (maybe down, but that would be harder) and the highest tree would be the unstable tree (our current stable tree). This way there would be binaries (GRP) on each tree except unstable. Of course, this is not continuously updateable as debian is. However, is can be argued that continuously updateable is not a "Good Thing" TM. So to recap, frozen trees with security updates would be a HUGE step towards a binary based distro. After the frozen trees all we need to do is expand our GRP offerings. BTW, the nice thing about this is that even if a binary isn't available on your tree, you can still always use good ole source packages. AND, if one of the binaries isn't built the way you like, just rebuild it from source. What do you think? Nathaniel -- gentoo-releng@gentoo.org mailing list