Date: Wed, 06 Jun 2012 22:27:01 -0700 From: Dave Hayes <dave@jetcafe.org> To: Doug Barton <dougb@FreeBSD.org> Cc: freebsd-stable@FreeBSD.org, Daniel Kalchev <daniel@digsys.bg> Subject: Re: Documenting 'make config' options Message-ID: <201206070527.q575R1sX052893@hugeraid.jetcafe.org> In-Reply-To: <4FCFC846.5050508@FreeBSD.org> References: <CAOgwaMvsv3e1TxDauV038Pp7LRiYeH7oAODE%2Bw-pxHt9oGrXMA@mail.gmail.com> <201206020012.q520CEcf057568@hugeraid.jetcafe.org> <20120602004230.GA14487@in-addr.com> <201206040224.q542OBqk085897@hugeraid.jetcafe.org> <20120604043233.GB32597@lonesome.com> <201206040841.q548fVHa091169@hugeraid.jetcafe.org> <CADLo83-9jE1zAtdXrA78=K5AE7yR4UsMh=efeC5L4kXijaDFaQ@mail.gmail.com> <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>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Barton <dougb@FreeBSD.org> writes: > 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? Personally, a 'pkg-options-descr' text file would suit me just fine. I don't claim this is a good or bad idea from the general perspective of FreeBSD users as a group. ;) From that perspective, the menu example suggested by Warren Block is decent; perhaps with an added button to "reset to defaults". From a quick persual of dialog(1), I'm sure something similar in functionality could be used without having to modify dialog itself. My loose attempt at requirements is that "enough" information about each option be in one place in the port skeleton to make an informed decision about whether to turn that option on or off. There should be a clear paragraph explaining what the option does, what consequences it might have if you enable/disable it, and why the default was chosen. BTW, thank you for changing the subject line. -- Dave Hayes - Consultant - Altadena CA, USA - dave@jetcafe.org >>> The opinions expressed above are entirely my own <<< Never promise, even by implication, without fulfilling your promise. The only acceptable alternative to completing an undertaking is to over-fulfil it. To betray any promise, explicit or otherwise, will harm you more than it can harm anyone else.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201206070527.q575R1sX052893>