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.
What I was trying to point out was that Courier's own stock configuration files don't "follow the rules". Every time I update, a handful of comment lines get moved around. The diff that was attached was one example of where that happens. Wherever you are using lines of '#' marks, the configs get munged. > sysconftool worked fine for many years. This is the first instance where > there was some pain. I don't mean to imply that a couple of missing settings constitute pain, but I've disliked sysconftool as long as it's been around. :) Since the init script changes required to handle configurations the way that I want are pretty minor, I may just go my own way on this one. Thanks for considering it, though. ------------------------------------------------------------------------- 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
