Re: [desktop] Unix configuration nightmare
>>"Branden" == Branden Robinson <email@example.com> writes:
Branden> On Wed, Oct 23, 2002 at 10:09:58PM +0200, Andreas Metzler wrote:
>> Time for a third opinion: I think your setup circumvents the problem
>> (parsing XF86Config) _very_ nicely with little overhead. It allows me
>> to customize any section I want while still letting debconf handle the
>> rest. Basically I just have to copy it and move it outside of the debconf
Branden> Well, that was the use case I had in mind when I wrote
Branden> XFree86's debconf support, but judging by the dozens of
Branden> config files I've seen, that's not the use case in widest
Branden> Cutting and pasting a block of text is Too Hard.
Perhaps you should add that to the comment: that the unit to
copy is a section; and any section may be copied at will.
Branden> The scenario you enjoy will die, because People Will Not
Branden> Read. It's also arguably a violation of way Debconf is
Branden> supposed to work (there's not supposed to be any such thing
Branden> as a "debconf area", and for files that aren't as
Branden> potentially insanely complex as XF86Config, I agree), so I'm
Branden> not getting any support from the Orthodox Church of Debconf,
Perhaps the solution is to grab the area between the debconf
markers, store a md5sum of that area, and act like dpkg does with
conffiles: allow the user to accept, refuse, view diffs, of the
section inside the debconf area.
Once I get ucf cleaned up and insert the diff3 functionality
in there, you can use ucf to really preserve user changes.
People will do tomorrow what they did today because that is what they
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C