Re: Documenting 'make config' options

2012-06-08 Thread Dan Daley
Thanks. I'll check this script out. From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG; Dan Daley ; Charles Sprickman ; Warren Block ; Vincent Hoffman Sent: Fri, June 8, 2012 2:47:37 AM Subject: Re: Documenting 'make config' options D

Re: Documenting 'make config' options

2012-06-08 Thread Oliver Fromme
Dan Daley wrote: > I usually use portmaster to install ports. The options dialogs that pop > up are often for dependencies. The options dialog gives the name of the > port for which the options are being selected, but no description or > indication as to why this is being installed (this co

Re: Documenting 'make config' options

2012-06-07 Thread Daniel Kalchev
On 07.06.12 08:27, Dave Hayes wrote: Personally, a 'pkg-options-descr' text file would suit me just fine. I have considered this lack of information about port options myself. Sometimes, when installing "new" (to your understanding) software finding out what those options actually do and wh

Re: Documenting 'make config' options

2012-06-06 Thread Dave Hayes
Doug Barton 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 rea

Re: Documenting 'make config' options

2012-06-06 Thread Dan Daley
I usually use portmaster to install ports. The options dialogs that pop up are often for dependencies. The options dialog gives the name of the port for which the options are being selected, but no description or indication as to why this is being installed (this could be a dependency of a de

Re: Documenting 'make config' options

2012-06-06 Thread Charles Sprickman
On Jun 6, 2012, at 7:43 PM, Warren Block wrote: > 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

Re: Documenting 'make config' options

2012-06-06 Thread Warren Block
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',

Re: Documenting 'make config' options

2012-06-06 Thread Vincent Hoffman
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 >>> w

Re: Documenting 'make config' options

2012-06-06 Thread Glen Barber
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 com

Documenting 'make config' options

2012-06-06 Thread Doug Barton
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