From owner-freebsd-hubs@FreeBSD.ORG Wed Sep 10 20:14:47 2003 Return-Path: Delivered-To: freebsd-hubs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8A08E16A4BF for ; Wed, 10 Sep 2003 20:14:47 -0700 (PDT) Received: from coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A96F43FB1 for ; Wed, 10 Sep 2003 20:14:46 -0700 (PDT) (envelope-from jonny@jonny.eng.br) Received: from jonny.eng.br (RJ174002.user.veloxzone.com.br [200.149.174.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by coe.ufrj.br (Postfix) with ESMTP id 3883F57D832; Thu, 11 Sep 2003 00:14:43 -0300 (BRT) Message-ID: <3F5FE8A9.5010006@jonny.eng.br> Date: Thu, 11 Sep 2003 00:14:49 -0300 From: =?ISO-8859-1?Q?Jo=E3o_Carlos_Mendes_Lu=EDs?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: pt-br, en-us, en, pt MIME-Version: 1.0 To: Ken Smith References: <20030911030455.GA3493@electra.cse.Buffalo.EDU> In-Reply-To: <20030911030455.GA3493@electra.cse.Buffalo.EDU> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: freebsd-hubs@freebsd.org Subject: Re: Change in layout? X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Distributions Hubs: mail sup ftp List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Sep 2003 03:14:47 -0000 Ken Smith wrote: > I have been "asking around" to see if this is possible. They haven't > said it's possible yet, but they haven't said it's not possible either. > So, IF it turns out this is possible do you think this would help? > > 1) Move the *release* package set into the releases/ directory > itself, instead of that being a symlink. Wouldn't this make those who download entire release dir to get almost 5G? And also, in these times when we donwload ISO images, is this a problem? > 2) Move the non-release package sets (e.g. packages-5-current) to > a new directory named releases/ You meant packages here, right? I like this idea. > Using the 4.9 release as an example that means the package set that > would be placed in ports/i386/packages-4.9-release under the current > scheme would be placed in releases/i386/4.9-RELEASE/packages instead. > > The reasons I thought this might help are: > > - the releases/ directory continues to be "static" stuff, with some > clever rsync scripts or the separate cvsup collections available > you can continue to just sync that during active release times if > you want > > - the ports/ directory will only contain "dynamic" stuff, and only > stuff directly related to the operations of "ports" (a tarball > of the /usr/ports tree, plus all the distfiles) > > - the packages/ directory (new) will contain only "dynamic" stuff, > and there will be less of it because the (static) release package > sets will now be in the releases/ directory > > This should make choosing to carry only ports stuff or only packages stuff > easier if you want to do that. > > Is this worth pursuing? They may still say no - keep in mind releases > are built by different people than the ports/packages, etc. and > coordinating it amongst all the different people during a time they're > all under stress (release time...) might not work. It needs some changes (and I don't know whici), but it's worth trying. Jonny -- João Carlos Mendes Luís - Networking Engineer - jonny@jonny.eng.br