Date: Wed, 06 Jun 2012 22:26:59 -0500 From: Dan Daley <dddaley@yahoo.com> To: Charles Sprickman <spork@bway.net> Cc: Warren Block <wblock@wonkity.com>, freebsd-stable@freebsd.org, Vincent Hoffman <vince@unsane.co.uk> Subject: Re: Documenting 'make config' options Message-ID: <4FD01F83.2080207@yahoo.com> In-Reply-To: <470F2F8A-BB03-4561-B085-9E108613DEF2@bway.net> References: <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> <20120606212351.GB1387@glenbarber.us> <4FCFD05C.6040707@unsane.co.uk> <alpine.BSF.2.00.1206061723370.17060@wonkity.com> <470F2F8A-BB03-4561-B085-9E108613DEF2@bway.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 dependency of some dependency of the port I am installing). It's probably too much for this dialog to show why this port is being installed (what other port required this port that is being installed), but a description of what this current port is would be helpful. But, if possible, some breadcrumb across the top showing the dependencies which prompted this install would be great: Port A --> Port B --> Port C --> Current Port for which options are being chosen On 06/06/2012 21:47, Charles Sprickman wrote: > 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 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> <Cancel> >> >> --------------------------------------------- >> 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. > If we're talking about changing dialog(1), let's make sure there's also an "uncheck all"/"check all" option. > > I'm looking at you, ghostscript: > > wc -l /var/db/ports/ghostscript9/options > 315 /var/db/ports/ghostscript9/options > > Charles > >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- > Charles Sprickman > NetEng/SysAdmin > Bway.net - New York's Best Internet www.bway.net > spork@bway.net - 212.655.9344 > > > > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FD01F83.2080207>