Date: Thu, 10 Feb 2000 14:14:09 -0600 From: Richard Wackerbarth <rkw@dataplex.net> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: freebsd-ports@freebsd.org Subject: Re: /usr/ports/ too big? Message-ID: <00021017153702.00545@localhost.localdomain> In-Reply-To: <200002101945.LAA76120@apollo.backplane.com> References: <200002092123.NAA68515@apollo.backplane.com> <38A30EEE.F2BEDEA2@cvzoom.net> <200002101945.LAA76120@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 10 Feb 2000, you wrote: > :Here's what we can do. We keep all the "major" subdirectories in > :place, such as audio, devel, etc. BUT, instead of branching out into > :separate subdirectories, we can just put everything into the > :Makefile. > Ouch. I think this is a big mistake. The one-directory-per-port > scheme works extremely well, I agree. First, I don't think we want to destroy too much, if any, of the present structure. However, I don't see much of a problem putting patches, scripts, etc in one directory if that helps (I'm not sure that it does) But, I think we are losing too much if we "unload" the descriptions of the ports. I certainly don't want to have to load a file to learn that the x-whatever-widget port is for generating invoices in sanscrit on a C-Itho printer. OTOH, we don't want to try to put the patch files, etc into the part of the tree which is always "loaded". To do that doesn't save much in the way of resources. As a result, I propose that each major subgroup have its directory as now. Each port in that directory is represented by FILE which has the description and a reference to a distribution `ar` file of the rest of the present directory. By a little magic, the description file can be a Makefile that fetches the unloaded directory structure. If we keep the archive in text format, rcs/cvs/cvsup can handle to updates of the 'ar' files efficiently. -- 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?00021017153702.00545>