From owner-freebsd-questions@FreeBSD.ORG Tue Apr 20 13:15:40 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C433316A4CE for ; Tue, 20 Apr 2004 13:15:40 -0700 (PDT) Received: from serv03.inetworx.ch (serv03.inetworx.ch [212.254.227.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DEDE43D45 for ; Tue, 20 Apr 2004 13:15:40 -0700 (PDT) (envelope-from dev@eth0.ch) Received: from localhost (localhost.localdomain [127.0.0.1]) by serv03.inetworx.ch (Postfix) with ESMTP id 87AAA252D74 for ; Tue, 20 Apr 2004 22:15:39 +0200 (CEST) Received: from serv03.inetworx.ch ([127.0.0.1]) by localhost (serv03.inetworx.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 14711-01 for ; Tue, 20 Apr 2004 22:15:39 +0200 (CEST) Received: from serv04.inetworx.ch (serv04.inetworx.ch [212.254.227.197]) by serv03.inetworx.ch (Postfix) with SMTP id 4C204252D70 for ; Tue, 20 Apr 2004 22:15:39 +0200 (CEST) Received: from 217.162.71.141 (SquirrelMail authenticated user dev.eth0) by serv04.inetworx.ch with HTTP; Tue, 20 Apr 2004 22:15:39 +0200 (CEST) Message-ID: <3888.217.162.71.141.1082492139.squirrel@serv04.inetworx.ch> In-Reply-To: <20040420201228.GB35510@happy-idiot-talk.infracaninophile.co.uk> References: <3800.217.162.71.141.1082489038.squirrel@serv04.inetworx.ch> <20040420201228.GB35510@happy-idiot-talk.infracaninophile.co.uk> Date: Tue, 20 Apr 2004 22:15:39 +0200 (CEST) From: dev@eth0.ch To: freebsd-questions@freebsd.org User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Virus-Scanned: by amavisd-new at inetworx.ch Subject: Re: Using portsupgrade with make arguments X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Apr 2004 20:15:40 -0000 > On Tue, Apr 20, 2004 at 09:23:58PM +0200, dev@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[1], 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. I saw exactly that when upgrading gettext. :-) I'll put the args in pkgtools.conf. Thanks. Dave > 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. > > Cheers, > > Matthew > > [1] 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 > default settings. > > -- > Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks > Savill Way > PGP: http://www.infracaninophile.co.uk/pgpkey Marlow > Tel: +44 1628 476614 Bucks., SL7 1TH UK >