/etc/setup/setup.cfg ?

[Igor Pechtchanski]

On Mon, 10 Mar 2003, Max Bowsher wrote:

> Igor Pechtchanski wrote:
> > On Mon, 10 Mar 2003, Max Bowsher wrote:
> >
> >> Igor Pechtchanski wrote:
> >>> On Sun, 9 Mar 2003, Max Bowsher wrote:
> >>>
> >>>> Igor Pechtchanski wrote:
> >>>>> There have been bits of persistent state that people wanted to
> >>>>> store for setup.  I'm proposing an Xdefaults-style setup.cfg in
> >>>>> /etc/setup.  If we compile a list of things to go in there, I
> >>>>> could write a parser for it (I don't think it merits yacc, like
> >>>>> the one for setup.ini :-D).
> >>>>
> >>>> Ok, but we need to decide: Is this going to be user-edited, or
> >>>> setup-edited? I.e., there is no point in allowing comments, if they
> >>>> get removed every time setup re-writes the file.
> >>>
> >>> It doesn't seem hard to have setup remember the order of options in
> >>> the config file (which would also allow it to remember user
> >>> comments), so that when we write out the options, we can keep the
> >>> order.
> >>
> >> But why bother?
> >> Max.
> >
> > To make the file user-editable.
>
> More code / little benefit. The average user won't ever need to edit this.
> The non-average user can cope with the lines being forced into particular
> order.
> Max.

Max,

I'm less concerned about the lines themselves, and more about associating
comments with lines.  How would you like it if you edited the file, put
some comments in it, and then found that *all* your comments were, for
example, bunched up at the start of the script?  Either we disallow
comments, or we keep the order, IMO.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune