On Wed, 9 Feb 2000, 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?
I know this is a few days old, but I want to suggest this
anyway. Restructure the ports tree so that at the top level are languages
and then there are categories beneath that. Like this:
en/
archivers/
astro/
...
jp/
archivers/
astro/
...
And so forth. I do know that foreign (I speak English natively, therefore
everything else is foreign to me) have been seperated off into their own
directories, but still a straight CVSup on ports will fetch them.
Configuring CVSup to only get those non-language directories is both time
consuming and problematic if a new directory is added and nobody tells
you. This also takes a step towards removing the English bias that
clearly exists within the ports tree (and elseware).
I know this will only reduce the problem of an overly large ports tree for
some time, but this is a good idea anyway, especially from an
organizational standpoint.
Has this been discussed before? Will I be laughed to scorn?
Jamie
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
