Date: Sat, 12 Feb 2000 16:15:56 -0800 From: Jeremy Lea <reg@FreeBSD.ORG> To: Richard Wackerbarth <rkw@dataplex.net> Cc: Will Andrews <andrews@technologist.com>, freebsd-ports@FreeBSD.ORG Subject: Re: /usr/ports/ too big? Message-ID: <20000212161556.D51878@shale.csir.co.za> In-Reply-To: <00021215021001.02300@localhost.localdomain>; from rkw@dataplex.net on Sat, Feb 12, 2000 at 02:38:01PM -0600 References: <20000209215806.M99353@abc.123.org> <20000212142232.B14775@shadow.blackdawn.com> <38A5BE37.1965CB96@gorean.org> <00021215021001.02300@localhost.localdomain>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
On Sat, Feb 12, 2000 at 02:38:01PM -0600, Richard Wackerbarth wrote:
> 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.
How well does CVS handle ar files? ie, is a one line change a one line
diff... Remember, people need to maintain these, and we do that through
CVS. We *really* do not want to move away from a central port's
repository.
Personally, I like the idea of moving to a flat port 'delta'. Although
I'd go two steps further, and make COMMENT the first line of DESCR and
only have a single patch per port.
-Jeremy
--
FreeBSD - Because the best things in life are free...
http://www.freebsd.org/
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?20000212161556.D51878>