Hi Gioele, On Mon, Dec 23, 2024 at 08:34:57PM +0100, Gioele Barabucci wrote: > On 23/12/24 16:23, Daniel Gröber wrote: > > As an example I'm familiar with iproute2 moved it's default config from > > /etc/iproute2 to /usr/share/iproute2 in trixie, that is it actually *loads* > > the config from there, it's not just example files so in that case upstream > > patching or symlink trickery would be required to make the package > > conformant to this convention. > > > > I've tried arguing this is a blatant disregard of policy but that fell on > > deaf ears so far. > > How is that against policy?
Debian policy section 10.7.2: > Any configuration files created or *used* by your package must reside in > /etc, [...] (Emphasis mine) I recently also found rc_policy.txt section 3: > All configuration files must reside in /etc. > Is it against policy to have default config values hardcoded in a binary? No, but if there's a config file that the program actually reads it has to be in /etc. (Ok technically policy also allows to "put the files in /etc and create symbolic links to those files from the location that the package requires." ;) > Why things change if these hardcoded values are moved to a read-only file in > /usr? (The user/admin configuration is still in /etc.) Because traditionally the expectation has been that editable files are present in /etc. I don't think I've ever come across a package that violated this expectation before this recent empty-/etc push but perhaps others know of examples outside my bubble here? --Daniel
signature.asc
Description: PGP signature
