From owner-freebsd-ports@FreeBSD.ORG Thu Jan 8 17:56:56 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A60016A4CE for ; Thu, 8 Jan 2004 17:56:56 -0800 (PST) Received: from catseye.mine.nu (d207-81-17-215.bchsia.telus.net [207.81.17.215]) by mx1.FreeBSD.org (Postfix) with SMTP id 98C3143D73 for ; Thu, 8 Jan 2004 17:56:54 -0800 (PST) (envelope-from catseye@catseye.mine.nu) Received: (qmail 67998 invoked by uid 1001); 9 Jan 2004 02:01:00 -0000 Date: Thu, 8 Jan 2004 18:01:00 -0800 From: Chris Pressey To: freebsd-ports@freebsd.org Message-Id: <20040108180100.0da13630.cpressey@catseye.mine.nu> In-Reply-To: References: Organization: Cat's Eye Technologies X-Mailer: Sylpheed version 0.9.8a (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Call for feedback on a Ports-collection change X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2004 01:56:56 -0000 On Thu, 8 Jan 2004 19:49:25 -0500 Garance A Drosihn wrote: > I have been pondering a possible change for the way the ports > collection is done. I've done a little exploration into the > idea, but I thought I'd ask for more feedback before sinking > more time into it. I believe I have someone who would do much > of the actual work for this change, so I think I can make it > happen, but I want to know if the FreeBSD ports project would > be interested in this idea if I come up with some working > version. > > To keep this as a "doable" project, I also have a fairly > modest goal: Further reduce the inode-count of the ports > collection. That's it. There are many things which could > be done as a follow-on to this, but that's all I want to > try for right now. This sounds like it would be a simple job requiring no more than a file archiver like tar(1), were it not for the fact that the ports tree is cvsup'ed file by file. Maybe some sort of CVS->shar gateway server mirror thingy? You could cvsup to it to keep a shar'ed ports tree up to date, and any time you wanted to built an individual port, you'd just unshar it first... Just a random brainfart. -Chris