Le Tue, Sep 09, 2025 at 04:59:18AM +0200, Daniel Leidert a écrit : > > IMHO it would be more important to determine, how users that need those > MIME types in /etc/mime.types get it there. Having a system that would > allow users to e.g. install chemical-mime-info and having that package > drop the additional definitions so /etc/mime.types picks them up, would > solve your issue. Then users that really need them, can install them > and have to care about the clashes. Other users would not be affected.
Hi Daniel and everybody, indeed, fewer and fewer users even need /etc/mime.types at all. And the alternative systems such as `file` and shared-mime-info are not as strict as I am in terms of sticking to the IANA's decladed media types. I will not remove the existing chemical media types from /etc/mime.types so hopefully we will not need a system to support optional additions. I read the archived discussion from 1995 at https://www.mhonarc.org/archive/html/ietf-822/1995-05/msg00047.html and I think that some of the arguments can be reverted now. In 1995 it was said that creating a new top-level media type was extra work not worth the effort, as applications/* types can be vendor-agnostic, but in 2025, one can also argue that removing the chemical top-level media type is not worth the effort, and that it may be good to officialise it. If somebody wants to lead I am happy to support. Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Debian Med packaging team http://www.debian.org/devel/debian-med Tooting from home https://framapiaf.org/@charles_plessy - You do not have my permission to use this email to train an AI -
