On Wed, Aug 21, Ludwig Nussel wrote:
Thorsten Kukuk schrieb:
[...] In the first place, you need to adopt your packages. What you need to do and what you can do depends on your package. It's not possible to implement this with every kind of configuration file, but on the other side, there are many applications which supports this already, and it is only a question of the right configuration and maybe a little bit of tweaking it. We develop currently an universal, really flexible config file parser for config files more or less compatible with the ini file format, it's libeconf: https://github.com/parlt91/libeconf
This should make it much easier to port some applications to the new schema.
Any creative ideas for services that most likely won't use that lib? Thinking of apache for example.
I'm currently working on plans for the base system, so creating the infrastructure for PAM, adjust shadow, util-linux, netcfg etc. as first examples. I haven't looked at more advanced packages like openssh or apache yet. Get the infrastructure ready, adjust the first easy packages and continue with the more complicated ones. As upstream systemd maintainers want to archive the same, I still have the hope that we can also benefit from that and only need to adjust the path for the configuration file, and not have to do everything at our own alone. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Felix Imendoerffer, Mary Higgins, Sri Rasiah, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org