Re: Linuxconf
>> From debian-devel-request@lists.debian.org Wed Jun 3 18:19:21 1998
>> Resent-Date: 2 Jun 1998 17:03:22 -0000
>> Resent-Cc: recipient list not shown: ;
>> X-Envelope-Sender: spotter@kerem-byavneh.netmedia.net.il
>> Date: Tue, 2 Jun 1998 19:34:11 +0300 (IDT)
>> X-Sender: spotter@kerem-byavneh.netmedia.net.il
>> X-Mailer: Windows Eudora Pro Version 2.1.2
>> Mime-Version: 1.0
>> Content-Type: text/plain; charset="us-ascii"
>> To: Craig Sanders <cas@taz.net.au>, Jules Bean <jmlb2@hermes.cam.ac.uk>
>> From: Shaya Potter <spotter@kby.netmedia.net.il>
>> Subject: Re: Linuxconf
>> Cc: Raul Miller <rdm@test.legislate.com>, David Engel <david@ods.com>,
>> John Goerzen <jgoerzen@cs.twsu.edu>, debian-devel@lists.debian.org,
>> "Rev. Joseph Carter" <knghtbrd@earthlink.net>
>> Resent-Message-ID: <"Pvu8dC.A.zgG.aBDd1"@murphy>
>> Resent-From: debian-devel@lists.debian.org
>> X-Mailing-List: <debian-devel@lists.debian.org> archive/latest/5816
>> X-Loop: debian-devel@lists.debian.org
>> Precedence: list
>> Resent-Sender: debian-devel-request@lists.debian.org
>>
>> At 12:36 AM 6/3/98 +1000, Craig Sanders wrote:
>> >On Tue, 2 Jun 1998, Jules Bean wrote:
>> >
>> >> Of course it's viable. It just becomes a package maintainer
>> >> responsibility. In the vast majority of cases, the package maintainer
>> >> ought to be able to use the *same code* as the package itself for
>> >> parsing config files.
>> >>
>> >> In many well factored cases, this will be as simple as extracting
>> >> config.c or some similarly named file from the distribution and making
>> >> a few changes to it.
>> >
>> >no, it's not that simple.
>> >
>> >it needs to read and parse the config file, allow the user to manipulate
>> >it, and then write it back out again (if the user chooses to save any
>> >changes) WITHOUT losing any information, including comments and the
>> >order of the comments.
>> >
>>
>> I believe linuxconf will error out if it can't parse the config file.
>>
>> Craig, would you be happy if there was a built in exception handeling
>> mechanism into linuxconf that would give a nice error when linuxconf
>> couldn't parse a file.
Or better: it would prompt the adminster that is this what you want (y/n/edit with vi or emacs
or the built-in editor :)) ?
--j
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: