From owner-freebsd-questions@FreeBSD.ORG Wed Aug 15 12:18:23 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D18F16A419 for ; Wed, 15 Aug 2007 12:18:23 +0000 (UTC) (envelope-from cjk32@cam.ac.uk) Received: from ppsw-7.csi.cam.ac.uk (ppsw-7.csi.cam.ac.uk [131.111.8.137]) by mx1.freebsd.org (Postfix) with ESMTP id DE98413C457 for ; Wed, 15 Aug 2007 12:18:22 +0000 (UTC) (envelope-from cjk32@cam.ac.uk) X-Cam-SpamDetails: Not scanned X-Cam-AntiVirus: No virus found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from gw.cjkey.org.uk ([88.97.163.222]:1131 helo=[192.168.2.186]) by ppsw-7.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:465) with esmtpsa (PLAIN:cjk32) (TLSv1:DHE-RSA-AES256-SHA:256) id 1ILHpD-0003GB-PI (Exim 4.63) (return-path ); Wed, 15 Aug 2007 13:18:11 +0100 Message-ID: <46C2EF03.4040102@cam.ac.uk> Date: Wed, 15 Aug 2007 13:18:11 +0100 From: Christopher Key User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Nikola Lecic References: <46C20CB8.3010706@cam.ac.uk> <200708142245.l7EMjQ8o027148@smtpclu-2.EUnet.yu> <20070815083210.M54184@obelix.home.rakhesh.com> <200708150810.l7F8AJEv032092@smtpclu-2.EUnet.yu> In-Reply-To: <200708150810.l7F8AJEv032092@smtpclu-2.EUnet.yu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Rakhesh Sasidharan , freebsd-questions@freebsd.org Subject: Re: portupgrade question X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2007 12:18:23 -0000 Nikola Lecic wrote: > On Wed, 15 Aug 2007 08:36:53 +0400 (GST) > Rakhesh Sasidharan wrote: > > >> Nikola Lecic wrote: >> >> >>> Yes, options are not saved that way and Vim's default is with X11. >>> Please make sure that the following lines exist in >>> your /usr/local/etc/pkgtools.conf: >>> >>> MAKE_ARGS = { >>> 'editors/vim' => 'NO_GUI=yes', >>> [... options for other ports ...] >>> } >>> >>> Next time portupgrade will honour it (without -P/-PP options, of >>> course). >>> >> As far as I know, portupgrade won't honour this setting vim is >> upgraded as a dependency of some other port. (Please correct me if >> I'm wrong. I haven't tried this; its just something I read). >> > > At least with portupgrade-devel, that doesn't seem true. I read it > too, and the source was an unofficial blog. For example, I have: > > MAKE_ARGS = { > [...] > 'print/apsfilter' => 'PAPERSIZE=a4', > 'print/ghostscript-gpl' => 'A4=yes', > [...] > } > > ghostscript-gpl is a dependency of apsfilter. Now, ghostscript-gpl > needed update. I removed apsfilter for this testing purpose and: > > # portupgrade -NR apsfilter > [...] > ---> Installing 'apsfilter-7.2.8_3' from a port (print/apsfilter) > ---> Building '/usr/ports/print/apsfilter' with make flags: PAPERSIZE=a4 > [...] > ---> Upgrading 'ghostscript-gpl-8.57' to 'ghostscript-gpl-8.57_1' > (print/ghostscript-gpl) > ---> Building '/usr/ports/print/ghostscript-gpl' with make flags: A4=yes A4=yes > > >> So the /etc/make.conf option is better. >> > > It is definitively the most universal and IMHO it should appear in the > Handbook. > > I just like to keep all ports/packages upgrading options at the same > place (USE_PKGS, MAKE_ARGS, USE_PKGS_ONLY...). > > BTW, as far as I can recollect, as a global-honouring tool for ports > configuration, the most frequently quoted one along these lists was > ports-mgmt/portconf. > > Nikola Lečić > Thanks Nikola, Roland, Rakhesh, I've gone for a portconf based solution for now, although, when I get the chance, I'll try to test how portupgrade behaves wrt dependencies. I would prefer to use pkgtools.conf for several reasons: 1) It keeps all the ports related configuration together 2) MAKE_ARGS get echoed when things are being built, whereas arguments in make.conf don't seem to 3) If I run 'make install clean', I'd rather it built things as default, rather than just being an alternative to 'portupgrade -N' Regards, Chris