From owner-freebsd-ports@FreeBSD.ORG Wed May 30 21:36:15 2012 Return-Path: Delivered-To: ports@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 9CFC51065675; Wed, 30 May 2012 21:36:15 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id BB23F15263F; Wed, 30 May 2012 21:36:14 +0000 (UTC) Message-ID: <4FC692CD.2030609@FreeBSD.org> Date: Wed, 30 May 2012 14:36:13 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Kevin Oberman References: <4301C0E3-3C53-46E2-B5A5-7BD120CD775F@FreeBSD.org> <4FC5F794.9050506@gmail.com> <4FC68FC0.1010707@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, Vitaly Magerya Subject: Re: [HEADSUP] New framework options aka optionng 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: Wed, 30 May 2012 21:36:15 -0000 On 5/30/2012 2:33 PM, Kevin Oberman wrote: > On Wed, May 30, 2012 at 2:23 PM, Doug Barton wrote: >> On 5/30/2012 3:33 AM, Vitaly Magerya wrote: >>> Folks, when moving forward with optionsng, do we want to convert >>> NOPORTDOCS and NOPORTEXAMPLES to options everywhere? >> >> Absolutely not. By far the majority of users benefit from installing the >> docs and examples. Users who don't want them can continue to do what >> they've always done, configure it in make.conf. Adding OPTIONS for these >> would only cause confusion. > > I'll go one further and suggest that the vast majority who don't want > these features are building specialized systems and they know very > well what they are doing. A global setting for these would be > desirable, though, as someone building a specialized distribution for, > say, an embedded system, will want no docs or examples for any port. I > suspect it is ALMOST always an all or nothing issue, not per port. Exactly. And the global option already exists. If someone really did need this per port then portconf or similar make.conf gymnastics are available. The new OPTIONS stuff looks promising, and I think it's a step in the right direction. But please let's not try to make it a one-size-fits-all solution. Doug -- This .signature sanitized for your protection