- To: Craig Sanders <email@example.com>
- Cc: Shaya Potter <firstname.lastname@example.org>, David Engel <email@example.com>, John Goerzen Linux Expo Laptop <firstname.lastname@example.org>, email@example.com, Jules Bean <firstname.lastname@example.org>, "Rev. Joseph Carter" <email@example.com>
- Subject: Re: Linuxconf
- From: Raul Miller <firstname.lastname@example.org>
- Date: Mon, 1 Jun 1998 21:56:04 -0400
- Message-id: <19980601215604.P3613@test.legislate.com>
- Mail-followup-to: Craig Sanders <email@example.com>, Shaya Potter <firstname.lastname@example.org>, David Engel <email@example.com>, John Goerzen Linux Expo Laptop <firstname.lastname@example.org>, email@example.com, Jules Bean <firstname.lastname@example.org>, "Rev. Joseph Carter" <email@example.com>
- In-reply-to: <Pine.LNX.3.96.980602111237.22947Afirstname.lastname@example.org>; from Craig Sanders on Tue, Jun 02, 1998 at 11:18:09AM +1000
- References: <19980601210338.N3613@test.legislate.com> <Pine.LNX.3.96.980602111237.22947Aemail@example.com>
> > So support the full grammar of the file.
Craig Sanders <firstname.lastname@example.org> wrote:
> debian currently has 1956 packages. most of them require a config
> file. do you think having that many individual parsers is viable?
(1) We don't have that many packages which require configuration
(2) Yes, I think it's viable to have a parser for each package which
requires configuration. [Or, several packages may share a parser if that
If that's not viable it's probably better to introduce a new config
file format for everybody than to introduce a scheme which is
a mix of several config file formats one of which is too complicated
for linuxconf to deal with.
> however, it's a problem which is inherent to non-templated
> configuration tools. linuxconf hasn't changed the way it operates, so
> at best it will have made the parsers a bit smarter but not eliminated
> the problem entirely.
I think it's also reasonable for linuxconf to present a dialog
to the effect that the configuration is beyond its ken, and it
has a choice of either replacing it entirely or doing nothing.
But you can do a lot with a decent parser.
> this issue was discussed at length last year in the debian-admintool
> list. check the archives from May '97.
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org