From owner-freebsd-stable@FreeBSD.ORG Wed Jun 6 23:43:44 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5D11F106567B for ; Wed, 6 Jun 2012 23:43:44 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 13A408FC12 for ; Wed, 6 Jun 2012 23:43:43 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q56NhagJ017284; Wed, 6 Jun 2012 17:43:36 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q56NhaiV017281; Wed, 6 Jun 2012 17:43:36 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 6 Jun 2012 17:43:36 -0600 (MDT) From: Warren Block To: Vincent Hoffman In-Reply-To: <4FCFD05C.6040707@unsane.co.uk> Message-ID: 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> <20120606212351.GB1387@glenbarber.us> <4FCFD05C.6040707@unsane.co.uk> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Wed, 06 Jun 2012 17:43:36 -0600 (MDT) 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 23:43:44 -0000 On Wed, 6 Jun 2012, Vincent Hoffman wrote: > On 06/06/2012 22:23, Glen Barber wrote: >> 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. :) >> > Not something I had bothered looking up till now as I hadnt wanted to > use it but the 2nd hit on google, > http://lists.freebsd.org/pipermail/freebsd-ports-bugs/2009-April/161673.html > describes it quite well. > I tend to go with, If i dont know what it is, and its not default, I > probably dont need it. > Unless it looks interesting, then I google it ;) > > Maybe an (optional) new file with a longer descriptions of the make > options so as not to crowd the make config dialog? > I dont mind looking up compile time options for software I am installing > but I can see how having a precis available locally might be handy. Here's an idea: if the description is too long to show in the very limited space, cut it off, show a "...", and show the entire description in a two- or three-line text box below the main one. The >< indicate a highlight here: ----------------------------------------------- >[ ] GOOFY Build with support for the... < [ ] EXAMPLES Install the examples ----------------------------------------------- < OK > --------------------------------------------- Build with support for the GOOFY framework that provides concurrent whoopsies integrated with a Perubython interpreter, and stuff. ----------------------------------------------- The description at the bottom is from whatever option is currently highlighted, and changes as the user scrolls through the options. It would be blank if the entire description could be displayed in the space available above. The advantage of this is that it would work with existing ports, and give the ability to use longer descriptions. The disadvantage is that dialog(1) would probably need modifications.