On Fri, Sep 27, 2024, at 11:31 AM, Florian Weimer wrote: > Do you see any problems if glibc starts using /usr/etc/services if > /etc/services does not exist? Please avoid having projects unconditionally read `/usr/etc` because on ostree based systems `/usr/etc/services` will always exist; we use it for our 3-way merge of /etc. (It's actually also really nice to have the defaults always visible, that's how `ostree admin config-diff` works) It will start to conflict if other projects put things there. Now our technical direction may go in a place where we move away from `/usr/etc` and do things differently (and this is a whole *other* big thing to align in api probably). Please use a project-specific namespace as you suggested below. > Same for /usr/etc/protocols, /usr/etc/rpc > and so on. It's already used on openSUSE, apparently. Hmmm. OK, messy. > Tracking upstream projects that do not support hermetic-usr for configuration > <https://github.com/uapi-group/specifications/issues/76> Now we have discussion of this split across 3 different forums; probably the glibc list is the best place to hash this out. -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
