Hi Charles, On 23.11.2013 05:34, Charles Plessy wrote: > I read the bug discussion and I am not sure to understand the problem that is > to solve. Isn't it enough to modify /etc/mimes.types ? If there were a > /etc/mime.types.d directory, which package would currently add some files > there ?
By policy files in /etc are to be modified by the user as you highlight. That being said, it's also guaranteed that changes are preserved across updates. Thus, if a user modifies that file, any future update would not be effective to that user, just because he had to add a custom mime type. That's not ideal, as we face a problem, where a file should be updated, but contain customizable additions aside. You already support this by reading .mime.types, but that's not a solution for daemons which (hopefully) do not rely on environment settings but are keen to start in a predictable configuration. Apache does it, Lighttpd does it and I assume many other daemons dealing with file types do as well. Usually they just read /etc/mime.types, and that's all they know about MIME types. On the other hand, how often did you actually change /etc/mime.type in the last years? Maybe it's a hypothetic problem anyway. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D
signature.asc
Description: OpenPGP digital signature
