On Mon, 12 Nov 2007 20:37:11 -0500
Chuck Robey <[EMAIL PROTECTED]> wrote:

> RW wrote:
> > On Mon, 12 Nov 2007 22:54:33 +0100
> > Tino Engel <[EMAIL PROTECTED]> wrote:

> > It's not hard to script it though, something like the following
> > would do
> > 
> > #!/bin/sh
> > for p in `pkg_version -ol'<' |awk '{ print $1 }'`; do
> >  cd  /usr/ports/${p} && make config-recursive 
> > done
> 
> I can't believe you actually suggested this.  



> First thing, it would take you HOURS to complete, 

Typically you can do  "make config-recursive"'s about 10-30 times per
minute on average - most installed ports have few  dependencies. It's
also only running over out-of-date ports, so it only takes minutes,
even for major upgrades.

I now use config-conditional which is faster, and works well enough in
practice not to warrant the extra time. 

> and you better not make even one mistake,
> 'cause you couldn't even go back far enough to figure out what the
> name was of the port you muffed.  

Both config-recursive and config-conditional use cached options where
availible. Options are pretty stable, so even in a major upgrade I only
see a few screens, and 90% of the time they are all trivial.

> Beyond that, since most ports ask
> questions formed with the name of the target dependency, aznd not
> asking things like "do you want such-and-such capability", so you
> have to be conversant with the names and capabilities of nearly
> 10,000 ports, to be able to do that job.

I find the one-line descriptions to be pretty good, and my experience
has been that if I don't understand an option, I don't need to change it
from the default. 

For the most part, I find that the more inscrutable options are internal
to the port, and have nothing to do with dependencies or any global
setting, for example the patch options in dns/djbdns. 


> Were you really seriously suggesting this.  It's so unworkable, its 
> laughable.

I've been doing it this way for a long time, it works fine.


_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to