On Wed, 9 Feb 2000, Matthew Dillon wrote:
>
> :> 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?
> :
> :Yes, this has been desired for some time, but without an actual
> :implementation we're kinda stuck. :)
> :
> :-Alfred
>
> It's a nice problem to have, I guess :-) I really like the idea of
> having a target overview. It would be utterly trivial to have a
> module list in the Makefile and to change the dependancies to run
> 'make modulename' in the parent directory rather then in the subdirectory
> (which might not exist). There's only one person who can make
> something like this happen.
Flattening out the unecessarily deep ports directory structure would help,
too. Probably, 98 percent of it could be done with a script, and it would
greatly decrease cvsup time and space.
----------------------------------------------------------------------------
Chuck Robey | Interests include C & Java programming, FreeBSD,
[EMAIL PROTECTED] | electronics, communications, and signal processing.
New Year's Resolution: I will not sphroxify gullible people into looking up
fictitious words in the dictionary.
----------------------------------------------------------------------------
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
