On Mon, Sep 28, Neal Gompa wrote:
Actually, a question to ask is: why do we need fillup? In Fedora, we don't use fillup at all for /etc/sysconfig files either, and people don't generally miss it. In fact, because we don't have it there, there's been a lot more effort to make things work without environment files or with layered configuration, because the fillup system doesn't exist as a crutch to avoid it.
The idea behind /etc/sysconfig was: admin changes it, we don't modify their changes, we don't remove their changes if the package gets deinstalled. And here fillup is necessary to add new variables to an existing file. fillup cannot remove variables as user configuration should never get deleted, even if the package gets removed. And here all the problems starts. Of course do we remove variables, and keeping them only confuses users, but does not help them. And of course packages changes, which would require a change in the sysconfig file. And of course do people de-install and re-install a package to start from scratch, means do a "reset" of that package configuration. Keeping the sysconfig file prevents this. When fillup got introduced over 20 years ago, it was a good thing at that time. When I wrote the first mail I also thought about a valid usecase for keeping /etc/sysconfig today. I haven't found one. My question would be: for what is /etc/sysconfig needed at all? In the end, we have {/usr},/etc/default, which solves all the problems very nicely. All my new projects will only use /etc/default, I don't see any sense in /etc/sysconfig anymore, which makes provides a real advantage or benefit. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org