A lot of people would reply that they'd like to configure the ports themselves before launching the installation, leading people to suggest scripts such as:
#!/bin/sh plist=`pkg_version -ovl'<' |awk '{ print $1 }'` for porg in $plist ; do cd /usr/ports/${porg} && make config-recursive done Before I go and annoy someone on the portupgrade list, does anyone here know if the portupgrade people have decided this is unnecessary functionality? Sincerely, -- Ned Ruggeri On Tue, Apr 15, 2008 at 8:49 AM, Manolis Kiagias <[EMAIL PROTECTED]> wrote: > > > > Pollywog wrote: > > > I did 'portupgrade -aP' last night but this morning I found that one > package had some questions for me about how I want to compile the package > (wants to know which options I want). This meant that no packages were > compiled since the cups package asked questions. > > > > Is there a way to circumvent this problem when upgrading with portupgrade? > > I know how to avoid this when installing a single port but not how to > avoid it when upgrading all available packages. > > > > > > thanks > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > > > > > > > > > Try the --batch option of portupgrade > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" > _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"