Using portsupgrade with make arguments
m.seaman at infracaninophile.co.uk
Tue Apr 20 13:12:35 PDT 2004
On Tue, Apr 20, 2004 at 09:23:58PM +0200, dev at eth0.ch wrote:
> just to get it clear for me: If I upgrade a port that has been originally
> installed with additional make arguments I must include them again. Is the
> following correct?
> Original installation:
> # make arg_1=val_1 arg_2=arg_2 install clean
> Upgrading port using portupgrade:
> # portupgrade -R -m "arg_1=val_1 arg_2=arg_2" port
If you still want the new version of the port to be built with those
arguments, yes. Instead of having to remember to type them in all the
time, add them to the MAKE_ARGS array in /usr/local/etc/pkgtools.conf
-- that way they'll be applied every time you upgrade the port.
There are now quite a few ports where that is strictly no longer
necessary. Those are the ports using the new 'OPTIONS' code committed
last January -- an example is devel/gettext. These ports will popup a
dialog box and record the settings you choose the first time you run
'make' in them, and then default to using those settings every time
you rebuild the port, or until an update to the port changes the set
of options available or until you run 'make config' again. However,
this only works for the ports that use the OPTIONS code.
You can mix both styles with impunity -- put entries into
pkgtools.conf as well as rely on the cached OPTIONS values -- I think
pkgtools.conf should override the OPTIONS cache, but you'll have to
experiment to be absolutely sure.
 If you don't want the dialogs to appear set BATCH=yes in the
environment or in /etc/make.conf This will automatically give you the
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20040420/8e6b2382/attachment.bin
More information about the freebsd-questions