Samuel Thibault, le jeu. 19 déc. 2024 10:26:12 +0100, a ecrit: > Gioele Barabucci, le jeu. 19 déc. 2024 10:22:02 +0100, a ecrit: > > On 19/12/24 10:19, Samuel Thibault wrote: > > > Gioele Barabucci, le jeu. 19 déc. 2024 10:15:47 +0100, a ecrit: > > > > * Admin can override the standard configuration via /etc/$proj/foo.conf > > > [...] > > > > Upstream projects are moving to this style. I hope that one day Debian > > > > packages will stop shipping files under /etc. > > > > > > Having pre-filled configuration files ready for editting in /etc > > > (possibly containing only commented lines) is extremely useful for > > > admins. > > > > $ cp /usr/lib/$proj/foo.conf /etc/$proj/ > > Which is not trivial, really.
Put another way: would it really be /usr/lib/$proj, or rather (since it's arch-independent) /usr/share/$proj, or rather (since that's documentation) /usr/share/do/$proj. How an admin would know? That's just hiding things, compared to the decades of habits. Also, /etc would thus be full of empty /etc/$proj directories? I don't see the point of not just putting the example files there? Why making it more difficult for the admin to configure their server? Samuel
