From owner-freebsd-ports@FreeBSD.ORG Mon Jun 22 14:01:34 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 8903C1065674 for ; Mon, 22 Jun 2009 14:01:34 +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 81A0F8FC08 for ; Mon, 22 Jun 2009 14:01:31 +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 9BFAD3096 for ; Mon, 22 Jun 2009 23:43:43 +1000 (EST) From: Nick Withers To: freebsd-ports@freebsd.org Content-Type: text/plain Date: Mon, 22 Jun 2009 23:43:38 +1000 Message-Id: <1245678218.97200.18.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: 9BFAD3096.23B8D X-nickwithers-MailScanner: Found to be clean X-nickwithers-MailScanner-From: nick@nickwithers.com Subject: 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 14:01:34 -0000 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). So, to get to my point: Would it be a good thing for unknown options in ports' options files to be removed automatically during the make (or somewhere else?)? Would it be better to redisplay ports' OPTIONS dialogues both on addition and on removal of OPTIONS? Should I just shut up? I don't really want to clear all ports options before each portmaster / portupgrade run, but for now I'm inclined to to reduce the risks of having weird and wonderful options set. In case it matters, this is what I ended up with in "/var/db/ports/ruby/options" after a "make config", not changing options but selecting "OK" (note the "ruby+nopthreads" bits): ____ # This file is auto-generated by 'make config'. # No user-servicable parts inside! # Options for ruby+nopthreads-1.8.7.160_3,1 _OPTIONS_READ=ruby+nopthreads-1.8.7.160_3,1 WITHOUT_ONIGURUMA=true WITH_IPV6=true WITHOUT_RDOC=true WITHOUT_DEBUG=true ____ -- Nick Withers email: nick@nickwithers.com Web: http://www.nickwithers.com Mobile: +61 414 397 446