Hi Sebastian. I just came to wonder,... what is the template.d actually good for? Isn't it the same what we already have with /etc/template ?
And even if you planned /etc/template.d as "for use by other packages only", we have some issues left: - we'd need the same for the check_commands dir, and the special templates dir - nothing actually prevents users from using /etc/template.d nevertheless, which means one could still get into troubles, when other packages actually put something there e.g. the apache packages have similar directories (e.g. sites-available, mods-available, etc.), where packages (but also users) put their snippets into. They do not specially try to avoid conflicts between a users personal files and name-collision by files from other debian packages. If that's your concern, than this is actually a much bigger problem in Debian, which affects not only config files of so many packages, but also things like user/group names. Cheers, Chris.
smime.p7s
Description: S/MIME cryptographic signature
