From owner-freebsd-stable@FreeBSD.ORG Wed Jun 6 21:23:54 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46428106564A for ; Wed, 6 Jun 2012 21:23:54 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from glenbarber.us (onyx.glenbarber.us [199.48.134.227]) by mx1.freebsd.org (Postfix) with SMTP id DEC8A8FC08 for ; Wed, 6 Jun 2012 21:23:53 +0000 (UTC) Received: (qmail 30080 invoked by uid 0); 6 Jun 2012 17:23:53 -0400 Received: from unknown (HELO glenbarber.us) (75.146.225.65) by 0 with SMTP; 6 Jun 2012 17:23:53 -0400 Date: Wed, 6 Jun 2012 17:23:51 -0400 From: Glen Barber To: Doug Barton Message-ID: <20120606212351.GB1387@glenbarber.us> References: <201206040224.q542OBqk085897@hugeraid.jetcafe.org> <20120604043233.GB32597@lonesome.com> <201206040841.q548fVHa091169@hugeraid.jetcafe.org> <201206041841.q54IfUow001060@hugeraid.jetcafe.org> <20120604191343.GF10783@isuckatdomains.isuckatdomains.net> <201206041932.q54JWONA001600@hugeraid.jetcafe.org> <4FCDA15C.2000700@digsys.bg> <201206061859.q56IxvLx045828@hugeraid.jetcafe.org> <4FCFC846.5050508@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FCFC846.5050508@FreeBSD.org> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-stable@freebsd.org Subject: Re: Documenting 'make config' options X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jun 2012 21:23:54 -0000 On Wed, Jun 06, 2012 at 02:14:46PM -0700, Doug Barton wrote: > On 06/06/2012 11:59, Dave Hayes wrote: > > I'm describing more of a use case here, not attempting to specify an > > implementation. If a user invokes 'make', a window is presented to them > > with various options. It's probably very common that this is met with an > > initial reaction of "what the hell do these do?", even from the most > > seasoned of admins (presuming they are unfamiliar with the software they > > have been asked to install). I claim it would be an improvement to have > > that information at the fingertips of the make invoker. > > What manner of providing this information would meet your needs? > IMHO, something informing what "THAT" is in devel/subversion option MOD_DONTDOTHAT would be nice. :) Glen