Sam Varshavchik wrote: > Gordon Messmer writes: >> sysconftool also tends to munge comments in configuration files. >> Anywhere there's a line of '#' characters used as a separator, for >> instance, that line and anything in between it and the name of a >> setting will be moved into the comment section for the previous >> section on upgrade. > > You just can't scribble over a sysconftool-managed file, freehand. The > sysconftool files must follow a certain structure. sysconftool's man > pages go into some detail. So, yes, if you freely edit the file, the > next time sysconftool touches it, it'll eat your changes, if you do not > follow the rules.
Obviously users (I for one) don't easily grasp what those rules are, let alone why they are there. >> [...] > sysconftool worked fine for many years. This is the first instance where > there was some pain. I see no reason for drastic changes. IMHO, installation would be more user friendly if a rule-checker tool could ensure consistency, so that make install-configure fails before sysconftool runs, if any file is not compliant. See also: [patch] Sysconftool silently deletes comments in config files Mon, 31 Jul 2006 12:17:10 -0700 http://www.mail-archive.com/[email protected]/msg27236.html ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
