From owner-freebsd-ports@FreeBSD.ORG Tue Sep 5 17:14:31 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5D0E16A4E1 for ; Tue, 5 Sep 2006 17:14:31 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.FreeBSD.org (Postfix) with SMTP id F395743DA4 for ; Tue, 5 Sep 2006 17:14:24 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 18857 invoked by uid 399); 5 Sep 2006 17:14:24 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 5 Sep 2006 17:14:24 -0000 Message-ID: <44FDB06D.8000307@FreeBSD.org> Date: Tue, 05 Sep 2006 10:14:21 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: B Briggs References: <44FC6EFC.2020208@bellsouth.net> In-Reply-To: <44FC6EFC.2020208@bellsouth.net> X-Enigmail-Version: 0.94.1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-ports@freebsd.org, r.c.ladan@gmail.com Subject: Re: portmaster: make config-conditonal ? 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: Tue, 05 Sep 2006 17:14:31 -0000 B Briggs wrote: > Rene Ladan wrote: >> Hi, >> >> what about the idea of using 'make config-conditional' instead of 'make >> config' in portmaster to configure ports? This way >> /var/db/ports/*/options is respected. >> >> The downside is that you have to run 'make rmconfig' in order to >> reconfigure the port options. >> >> Regards, >> Rene > > I second that emotion! > > or possibly use config-conditional in -u unattended mode, and config > otherwise. The problem with doing that is that there is (what I consider to be) a bug in the OPTIONS framework where if you have an existing /var/db/ports/ file for that port, but the Makefile introduces a new option, config-conditional will not re-run config to allow you to twiddle the new option. I did extensive testing with the various combinations of targets before settling on the method I chose. Doing it the way I have is the only way to be absolutely sure that you can set each option, even if new ones are added. FWIW, I would really like to see the OPTIONS framework improved to handle this, and other bugs; since I would like to be able to do what you guys described here too. :) hth, Doug -- This .signature sanitized for your protection