Re: dselect configurability (was Re: Galloping Featurism)
'Ian Jackson wrote:'
>
>Chris Fearnley writes:
>> John and I have
>> thought about the issues raised in several of the debian-devel
>> discussions and have concluded that dselect needs a menu to set some
>> high-level installation parameters. We have written a sample menu
>> config file and a simple parser for it. Hopefully we can find time
>> over the next several weeks to merge this work into dselect. Here is
>> our "selectmenu.cfg":
>> [stuff]
>
>This is very interesting. I'd like to make a few comments:
>
>* grep -i through the source for the string `fixme configurable'.
>This marks hard-coded values that I think should be configurable.
We found a couple of those :)
>* I was planning to add a series of configuration variables which
>would be settable using command line options or in an rc file; this is
>a fairly easy extension to myopt.[ch].
Perhaps that is the way to do it. I was thinking of making at least
the selection of priority be settable from a menu where it is out in
the open -- available to the user.
>It seems to me that your menu-based scheme might do well to edit the
>rc file.
Or read the rc-file to decide which menu-selections to make "default".
The selectmenu.cfg would be a configuration file for this extra
dselect menu in our scheme.
--
Christopher J. Fearnley | Linux/Internet Consulting
cjf@netaxs.com, cjf@onit.net | UNIX SIG Leader at PACS
http://www.netaxs.com/~cjf | (Philadelphia Area Computer Society)
ftp://ftp.netaxs.com/people/cjf | Design Science Revolutionary
"Dare to be Naive" -- Bucky Fuller | Explorer in Universe
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: