From owner-freebsd-ports@FreeBSD.ORG Mon Jun 22 23:16:38 2009 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CF941065672 for ; Mon, 22 Jun 2009 23:16:38 +0000 (UTC) (envelope-from nick@nickwithers.com) Received: from mail.nickwithers.com (mail.nickwithers.com [123.243.228.66]) by mx1.freebsd.org (Postfix) with ESMTP id 2E9778FC0A for ; Mon, 22 Jun 2009 23:16:36 +0000 (UTC) (envelope-from nick@nickwithers.com) Received: from [10.0.0.249] (nehalem.shmon.net [10.0.0.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.nickwithers.com (Postfix) with ESMTPSA id 79A483052; Tue, 23 Jun 2009 09:16:21 +1000 (EST) From: Nick Withers To: Doug Barton In-Reply-To: <4A4007A0.3040606@FreeBSD.org> References: <1245678218.97200.18.camel@nehalem.shmon.net> <4A4007A0.3040606@FreeBSD.org> Content-Type: text/plain Date: Tue, 23 Jun 2009 09:16:11 +1000 Message-Id: <1245712576.1146.4.camel@nehalem.shmon.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-MailScanner-ID: 79A483052.E6955 X-nickwithers-MailScanner: Found to be clean X-nickwithers-MailScanner-From: nick@nickwithers.com Cc: freebsd-ports@freebsd.org Subject: Re: Removed port OPTIONS linger in /var/db/ports/.../options X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jun 2009 23:16:38 -0000 On Mon, 2009-06-22 at 15:37 -0700, Doug Barton wrote: > Nick Withers wrote: > > Hello all! > > > > I was surprised to see, when trying to update lang/ruby18 today, that > > the to-be-installed package would be named "ruby > > +nopthreads-1.8.7.160_3,1", rather than the expected > > "ruby-1.8.7.160_3,1". > > > > Checked out the port's Makefile, and indeed this name is now set when > > "WITHOUT_PTHREADS" is defined. Righto, no worries. > > > > I hadn't defined WITHOUT_PTHREADS though... Or at least, didn't think I > > had! "make config" for lang/ruby18 didn't even show such an option. > > > > "/var/db/ports/ruby/options", however, did, left over from a while back: > > ____ > > > > # This file is auto-generated by 'make config'. > > # No user-servicable parts inside! > > # Options for ruby-1.8.7.72_1,1 > > _OPTIONS_READ=ruby-1.8.7.72_1,1 > > WITHOUT_PTHREADS=true > > WITHOUT_ONIGURUMA=true > > WITHOUT_GCPATCH=true > > WITH_IPV6=true > > WITHOUT_RDOC=true > > WITHOUT_DEBUG=true > > ____ > > > > I must admit, I thought that when options were added or removed, the > > OPTIONS dialogue was redisplayed automatically, but it seems this is > > only when options are added (consistent with what seems to be implied in > > http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html). > > If that's accurate then it's a bug, although IME the cases where an > option is removed are few and far between. It'd be handy if I were to file a PR, then? This'd be the first time I've knowingly hit the problem. > > I don't really want to clear all ports options before each > > portmaster / portupgrade run > > You don't need to clear them all with portmaster, you can use the > --force-config option which will run 'make config' for each port but > preserve the choices you've already made. Good point (I'd have to make sure to select "OK" rather than "Cancel" too, but that's pretty easy!). I update my ports pretty regularly (daily or more frequently, often enough) and with a thousand-odd ports on a couple of desktop machines, --force-config (or portupgrade's -C / --config)'s gonna get old pretty quick! > There is also the > --check-port-dbdir option if you want to clear out options files for > ports you're no longer using. That's a nifty one I wasn't aware of, cheers. > hth, > > Doug -- Nick Withers email: nick@nickwithers.com Web: http://www.nickwithers.com Mobile: +61 414 397 446