Am Fr., 27. Sept. 2024 um 11:33 Uhr schrieb Florian Weimer <fweimer@xxxxxxxxxx>: > > Do you see any problems if glibc starts using /usr/etc/services if > /etc/services does not exist? Same for /usr/etc/protocols, /usr/etc/rpc > and so on. It's already used on openSUSE, apparently. > > And alternative proposal was to use /usr/share/services (which I really > dislike), or /usr/share/nss/services (to which I do not have any > objections). Is OpenSUSE the only precedent so far? I'd say we should look at the bigger picture: moves to /usr were motivated (and justified) by the fact that we think of /usr as "tied" to the state of the system installation, that is everything that is rolled back when an installation is rolled back to a different state, modified at install and update time, unchanged/immutable otherwise. /etc is there to provide or override config. Where does the config live that we override from /etc? If the files we want to move are not "host specific" (otherwise we couldn't move them to in stall-specific, host-agnostic /usr) and not arch-specific then /usr/share seems to make sense. /ust/etc looks like redefining the meaning of "etc", which we could, of course, but hopefully on common grounds with other distros :) Michael -- _______________________________________________ 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