On 02/01/2019 08:58, ChenQi wrote:
Hi Jonas,
Cleaning up systemd's /etc files while leaving other softwares requiring
/etc files is not that pleasant. At a minimum, systemd users who are not
aware of this 'stateless' concept would be confused. "Where's my
/etc/systemd/system.conf file?!" They would ask.
How about this:
In order to support both the "stateless" variant where /etc/systemd does
not exist and the current situation where we have only the
(low-priority) top-level configuration files, we could do this:
i) Let systemd install its unmodified config files into /etc/systemd
ii) Provide configuration snippets in /usr/lib/*.conf.d
iii) Provide the overriding configuration snippet directories in /etc
with symlinks back up to the toplevel file, making the toplevel file
relevant again in case somebody is modifying it directly. i.e.:
/etc/systemd/journald.conf
/etc/systemd/journald.conf.d/00-systemd-conf.conf -> ../journald.conf
The important thing to get right here is to give the user an indication
that he should actually be putting stuff into the conf.d/ directory...
if they see that the directory exists they may go read the man page and
understand how these files are stacked.
Thoughts?
/Jonas
So I'd suggest using something like 'stateless' DISTRO_FEATURE (just
like 'usrmerge') to control each recipe's behavior.
Best Regards,
Chen Qi
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
