An even more radical approach, and more controversial, would
be to remove /usr/ports entirely and use the concept of source packages.
pkg_add -r aumix would install the binary, and something along the lines of:
pkg-source_add -r aumix would download the source, patches, and whatever else
needed.
Considering most of us out there, myself included, have fallen madly in love
with ports the way it is, I doubt that the current system won't go away
for a long, long time.
-Dan Papasian
<[EMAIL PROTECTED]>
On Wed, Feb 09, 2000 at 09:58:06PM +0100, Kai Voigt wrote:
> Hello,
>
> I'm just doing a cvsup update of my system and -as many times before- I
> realize that /usr/ports/ takes a lot of time and also disk space to sync.
>
> # du -sk /usr/ports
> 71118 /usr/ports
>
> Am I the only one being little annoyed by this fact? Would it make
> any sense to offer some "castrated" ports repository. Like putting
> a target "overview" into each /usr/ports/*/Makefile to list all available
> subdiretories. Then, with some other command, one could fetch the
> current port's directory from the cvs server to install the port.
>
> Do these thoughts make any sense?
>
> Kai
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
