From owner-freebsd-ports@FreeBSD.ORG Fri Dec 14 20:45:39 2007 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 23D1B16A417 for ; Fri, 14 Dec 2007 20:45:39 +0000 (UTC) (envelope-from skip@menantico.com) Received: from vms042pub.verizon.net (vms042pub.verizon.net [206.46.252.42]) by mx1.freebsd.org (Postfix) with ESMTP id E767313C455 for ; Fri, 14 Dec 2007 20:45:38 +0000 (UTC) (envelope-from skip@menantico.com) Received: from mx.menantico.com ([71.188.11.206]) by vms042.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JT200ATJ4B6QF37@vms042.mailsrvcs.net> for freebsd-ports@freebsd.org; Fri, 14 Dec 2007 14:45:06 -0600 (CST) Date: Fri, 14 Dec 2007 15:45:30 -0500 From: Skip Ford In-reply-to: <4762E71E.4040403@gmail.com> To: "Aryeh M. Friedman" Mail-followup-to: "Aryeh M. Friedman" , RW , freebsd-ports@freebsd.org Message-id: <20071214204530.GA812@menantico.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline References: <475F7390.9090509@gmail.com> <0F330142-A3CA-4E6E-84BD-FDE55A8E3AEE@yahoo.com> <20071213111050.O6078@wonkity.com> <200712140312.47837.danny@ricin.com> <4761F9E2.7090706@gmail.com> <20071214121906.1241dcdd@gumby.homeunix.com.> <4762E71E.4040403@gmail.com> User-Agent: Mutt/1.4.2.3i Cc: RW , freebsd-ports@freebsd.org Subject: Re: Limitations of Ports System 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: Fri, 14 Dec 2007 20:45:39 -0000 Aryeh M. Friedman wrote: > RW wrote: >> On Thu, 13 Dec 2007 22:34:58 -0500 "Aryeh M. Friedman" >> wrote: >> >>> Namely if I build abc with options 123 and 345 and def with 345 >>> and 678 then 345 will be cached for def since we already set it >>> for abc. >> >> How do you know the user wants 345 set on both ports? >> >> It might be a useful stable feature on "abc", but causes lock-ups >> on "def" > > There are multiple ways to handle the effects of 345 on def... only > one of them is to automatically apply it the other two are def can > ignore it by default or make it suer settable Other than the automatic caching apsect, how would this be any different from what we already have with ports-mgmt/portconf? Currently, if you want a knob to apply to all ports, you wildcard the knob in your ports.conf file. If you want the same knob defined differently depending on port name, you define it per port. -- Skip