RE: options handling when there are LOTS of options

["Larson, Timothy E." <TELarson%west.com@localhost>]

> On Wed, Jan 20, 2010 at 05:03:50PM -0600, Larson, Timothy E. wrote:
> > Is there a way to make package options take a value, rather than
> simple
> > binary (present/nonpresent) switches?  I've got a package with
> over 40
> > possible drivers. I think it would be a lot easier to take a
> > comma-delimited string and pass it straight to configure since
> that's
> > the kind of format it's expecting, than to construct such a string
> from
> > bunches of individual options.  Especially since its configure
> already
> > supports "all,!driver" syntax.
> 
> You can just build the string with .for or the :@ construct.

I'm not saying it _can't_ be done.  I'm saying that asking the user to type 39 
option flags when he wants all-but-one of the 40 available is a cruel joke, 
especially when configure will already support "all,!driver".  Maybe this type 
of case has been considered too unusual to build support for?

Tim

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
pkgsrc-wip-discuss mailing list
pkgsrc-wip-discuss%lists.sourceforge.net@localhost
https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-discuss