On Tuesday 20 February 2007 08:33, Ralf Corsepius wrote:
I don't see this - Separate config files only restrict the user to what a vendor wants him to restrict to and what the vendor has taken into consideration.
It takes away the freedom of customization and takes away the freedom extending init-scripts to what the vendor has not considered.
Why would this be useful? The user has chosen to customize, so it's the user's responsibility to handle this situation - If you take away %config you are simply erasing, killing his "carefully handcrafted solution" to a real world problem. - I can't find this helpful.
And I can't see any difference between this an any other script on the file system. So unless we extend it so that all editable scripts become %config, I don't see this special casing being helpful, instead its promoting upstreams to continue to use init scripts for configuration.