On Mon, Dec 12, Lee Duncan wrote:
So you expect upstream packages we use in openSUSE to create a layered configuration file system, since systemd does it that way?
Many upstream packages do that already, we just never really enforced, that package maintainers adjust their packages. See e.g. dbus.
The way I see it, I'd have to submit changes upstream to do this (ignoring the hours of work it would take), then hope they accept them, and if they do then other distributions using the code would have to change as well. And all to support some transactional model layered on top of Linux?
Not because of transactional update or something similar, there are many more reasons. Just read the blog mentioned in this thread or the old discussion on factory about this some years ago. And about upstream: my team made very good experience with this. We upstreamed many of our changes, and only once a maintainer refused the idea at all. Else all changes are upstream. Only today we got support for /etc/shells (/etc/shells.d, /usr/*/shells.d/, ...) upstream in Linux-PAM and util-linux, shadow is only waiting for some documentation adjustements. Latest if this https://uapi-group.org/ get's further this all about /etc will get a real boost. Thorsten
I guess at some point you're just going to have to quit supporting many packages then.
-- Lee Duncan Owner of half a dozen packages that use /etc for config files.
-- Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nuernberg, Germany Managing Director: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman (HRB 36809, AG Nürnberg)