Quoting Osamu Aoki (os...@debian.org): > > The current mechanism used by libnss-mdns for updating /etc/nsswitch.conf is > > not policy-compliant. > > Is it? > > Actually, I initially thought it was not policy-compliant without > looking into facts. But /etc/nsswitch.conf does not look like conffile. > It is a generated file by base-files.postinst. So, as long as > base-files and libnss-mdns maintainers cordinate each other, I see > no problem in terms of policy.
Oh, doh. Shouldn't it be a conffile anyway? As a local admin, I would hate seeing my carefully crafted nsswitch.conf file broken by packages' updates just because "it is policy-compliant as this is not a conffile". And I certainly know about Debian-haters who would happily use this as an argument to bash us for doing that (forgetting that most other distros happily break such files during upgrades...) So, well, sounds like a goodpolicy-compliant method to update nsswitch.conf would indeed be a great enhancemeent to bring. Thinking out loud, it could be something like /etc/nsswitch.conf.d/ but I'm not sure that's easy to do without hacking many things.
signature.asc
Description: Digital signature
