Your message dated Tue, 29 Apr 2014 13:07:22 +0900
with message-id <[email protected]>
and subject line Re: Bug#644227: Please add support for /etc/mime.types.d or
alternatives.
has caused the Debian Bug report #644227,
regarding Please add support for /etc/mime.types.d or alternatives
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
644227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644227
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lighttpd
Version: 1.4.28-2
Lighttpd gets its MIME configuration from output of
/usr/share/lighttpd/create-mime.assign.pl. This script only reads MIME
types from /etc/mime.types. However, the mime-support package also keeps
per-user MIME-types in ~/.mime.types. These are ignored in the Lighttpd
configuration, even if kept in www-data home-dir. The only way to add
new per-user MIME types that are also picked up by Lighttpd is through
/etc/mime.types, which is not recommended.
I propose that create-mime.assign.pl also reads .mime.types in the
home-dir of lighttpd user (lighttpd.conf::server.username)
--- End Message ---
--- Begin Message ---
Le Sat, Nov 23, 2013 at 05:22:47PM +0100, Arno Töll a écrit :
>
> 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.
Hi all,
I am closing the bug for the moment. Feel free to reopen it if you have a
concrete use case that can not be solved by modifyig /etc/mime.types either
directly in the mime-support package, or locally by the administrator.
Have a nice day,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
--- End Message ---
