From owner-freebsd-stable@FreeBSD.ORG Wed Jun 6 21:14:50 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 221B61065674 for ; Wed, 6 Jun 2012 21:14:50 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 76FC315FCAA; Wed, 6 Jun 2012 21:14:46 +0000 (UTC) Message-ID: <4FCFC846.5050508@FreeBSD.org> Date: Wed, 06 Jun 2012 14:14:46 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120506 Thunderbird/12.0.1 MIME-Version: 1.0 To: Dave Hayes References: <201206020012.q520CEcf057568@hugeraid.jetcafe.org> <20120602004230.GA14487@in-addr.com> <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> In-Reply-To: <201206061859.q56IxvLx045828@hugeraid.jetcafe.org> X-Enigmail-Version: 1.5pre OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Daniel Kalchev Subject: 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:14:50 -0000 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? -- This .signature sanitized for your protection