From owner-freebsd-ports@FreeBSD.ORG Thu Sep 18 19:18:20 2008 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E03B41065673 for ; Thu, 18 Sep 2008 19:18:20 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from lab.alexdupre.com (cl-506.trn-01.it.sixxs.net [IPv6:2001:1418:100:1f9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 10C898FC18 for ; Thu, 18 Sep 2008 19:18:19 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: (qmail 44492 invoked from network); 18 Sep 2008 19:18:18 -0000 Received: from unknown (HELO athlon.alexdupre.com) (192.168.178.2) by lab.alexdupre.com with SMTP; 18 Sep 2008 19:18:18 -0000 Message-ID: <48D2A979.7090809@FreeBSD.org> Date: Thu, 18 Sep 2008 21:18:17 +0200 From: Alex Dupre User-Agent: Thunderbird 2.0.0.16 (X11/20080726) MIME-Version: 1.0 To: John Baldwin References: <200809151036.19674.jhb@freebsd.org> <200809171303.05759.jhb@freebsd.org> <48D2167F.3040203@FreeBSD.org> <200809181033.56619.jhb@freebsd.org> In-Reply-To: <200809181033.56619.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, Doug Barton Subject: Re: OPTIONS handling doesn't seem to work fully in dependencies anymore 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: Thu, 18 Sep 2008 19:18:21 -0000 John Baldwin wrote: > Trust me, since I rebuild from scratch all the time, I quite remember when > options were first added and I'd kick off a build of kde or some such > overnight and check my screen session in the morning only find it hadn't > build hardly anything b/c it had popped up the option screen for gettext. :) Me, too, really :-) But kde3 meta-port doesn't use the OPTIONS framework, even if it displays the dialog box. And when the OPTIONS framework was added, very few ports actually used it, so it was very very rare to incur in *direct* dependencies between two OPTIONS-enabled ports. The kde4 meta-port now uses it, so it became obvious that something wasn't working as expected when you tried to build it. > I wonder why it has to be this hackish btw. Could config-conditional simply > be in the list of targets before 'fetch' or some such? I thought the same thing, probably yes, but I dunno why it was added in such way from the beginning, so I tried to create the simplest and surely working patch maintaining the current workflow. -- Alex Dupre