Date: Sat, 12 Feb 2000 14:38:01 -0600 From: Richard Wackerbarth <rkw@dataplex.net> To: Will Andrews <andrews@technologist.com> Cc: freebsd-ports@FreeBSD.ORG Subject: Re: /usr/ports/ too big? Message-ID: <00021215021001.02300@localhost.localdomain> In-Reply-To: <38A5BE37.1965CB96@gorean.org> References: <20000209215806.M99353@abc.123.org> <20000212142232.B14775@shadow.blackdawn.com> <38A5BE37.1965CB96@gorean.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 12 Feb 2000, Will Andrews wrote: > On Sat, Feb 12, 2000 at 11:15:04AM -0800, David O'Brien wrote: > > ... the conclusion was to use one dir per port > I haven't heard anything from Satoshi about this being in stone, so you > aren't entirely correct.. I hope that nothing is "in stone" yet. The one dir per port is a step in the right direction. However, I think the idea can be improved. I would suggest that we replace each port with a single FILE which contains a description and the designator of the port. The makefiles and patches, etc. for a particular port can then be kept in an 'ar'chive which gets expanded only while building. These archives don't even need to be fetched until someone wants to build the port. If we do that, I see no reason to not use a flat 'build-here' directory. Having such would certainly simplify housekeeping tasks like "clean" -- Richard Wackerbarth rkw@Dataplex.NET To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00021215021001.02300>