Bug#644227: lighttpd create-mime.assign.pl ignores ~/.mime.types

2011-10-04 Thread Magnus Olsson

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)







--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#644227: [pkg-lighttpd] Bug#644227: lighttpd create-mime.assign.pl ignores ~/.mime.types

2011-10-04 Thread Olaf van der Spek
On Tue, Oct 4, 2011 at 9:29 AM, Magnus Olsson mag...@minimum.se wrote:
 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)

Hi Magnus,

The www-data home dir is /var/www
This is certainly not the right place to put mime types.

What exactly does mime-support do?

Olaf



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#644227: [pkg-lighttpd] Bug#644227: lighttpd create-mime.assign.pl ignores ~/.mime.types

2011-10-04 Thread Olaf van der Spek
On Tue, Oct 4, 2011 at 10:27 AM, Magnus Olsson mag...@minimum.se wrote:
 On 10/04/2011 10:22 AM, Olaf van der Spek wrote:

 On Tue, Oct 4, 2011 at 10:17 AM, Magnus Olssonmag...@minimum.se  wrote:

 I want to add support for .json files which currently are treated as some
 kind of binary file by lighttpd.
 This is mostly a webserver extension, so I guess it also applies to
 apache

 It sounds like a global mime type, not restricted to the domain of web
 servers.

 and other webservers. I am unsure if these too use the /etc/mime.types
 files, if they do, it makes sense adding it to the mime-support package
 and

 I think they do.

 integrate .json files into upstream /etc/mime.types

 However, I also plan on using a custom file extension, for which I need a
 mime-type. I don't really care if it's per-user (as long as www-data
 counts
 as a user), per-daemon (as long as lighttpd is included) or system-wide
 way
 to define the mime-type for this custom file ext.. I simply need a way of
 doing it.

 With the current system, how do you suggest adding a new mime-type? The
 only
 way I see is editing /etc/mime.types, which will cause conflicts for
 every
 update of mime-support package.

 I've never needed to alter mime types, but you're right, editing
 mime.types isn't ideal.
 Unfortunately the file name and type of mime types is hard-coded (at
 least in Lighttpd), so I think there's no better option.
 Ideally there'd be a mime.user.types or so for the sys admin to use.

 A mime.user.types would be ideal. Do you propose adding this to lighttpd or
 should this be added to the mime-support package?

It's not Lighttpd specific, so it shouldn't be in the Lighttpd pkg.
Your best bet is to ask the developers of mime-support how this should
be handled properly.

Olaf



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#644227: lighttpd create-mime.assign.pl ignores ~/.mime.types

2011-10-04 Thread Stefan Bühler

On 10/04/2011 09:29 AM, Magnus Olsson wrote:

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.


Files in /etc are there to be changed. To avoid update conflicts, the 
mime-support package should be fixed to either allow additional config 
files in /etc (like /etc/mime.types.d) or to put the current data in 
/usr/share, and only have custom types in /etc/mime.types.



I propose that create-mime.assign.pl also reads .mime.types in the
home-dir of lighttpd user (lighttpd.conf::server.username)


Reading from any user home dir is certainly not an option.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#644227: lighttpd create-mime.assign.pl ignores ~/.mime.types

2011-10-04 Thread Magnus Olsson

On 10/04/2011 11:11 AM, Stefan Bühler wrote:

On 10/04/2011 09:29 AM, Magnus Olsson wrote:

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.


Files in /etc are there to be changed. To avoid update conflicts, the 
mime-support package should be fixed to either allow additional config 
files in /etc (like /etc/mime.types.d) or to put the current data in 
/usr/share, and only have custom types in /etc/mime.types.

I like the idea of a drop-directory!



I propose that create-mime.assign.pl also reads .mime.types in the
home-dir of lighttpd user (lighttpd.conf::server.username)


Reading from any user home dir is certainly not an option.





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#644227: [pkg-lighttpd] Bug#644227: lighttpd create-mime.assign.pl ignores ~/.mime.types

2011-10-04 Thread Arno Töll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

reassign 644227 mime-support
retitle 644227 Please add support for /etc/mime.types.d or alternatives
affects 644227 lighttpd
thanks

Hello,

On 04.10.2011 11:11, Stefan Bühler wrote:
 Files in /etc are there to be changed. To avoid update conflicts, the
 mime-support package should be fixed to either allow additional config
 files in /etc (like /etc/mime.types.d) or to put the current data in
 /usr/share, and only have custom types in /etc/mime.types.

Either one is a good idea I like. That's the right approach, and one
which also works globally. Unfortunately many packages may rely on a
single /etc/mime.types file, so I guess mime-support's maintainer would
need to add a update-mime-types helper or something which merges changes
upon request to a single file.

Having that said, I think this is not a problem specific to Lighttpd and
while it would be easy to implement that for us, because we do have a
mime.types wrapper already, I believe a proper solution would work for
any program relying on the mime.types file. Hence I reassign this bug to
to mime-support in hope maintainers there will agree.

If you there think this is not a more generic problem, please reassign
the bug back to us.

- -- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOitUpAAoJEMcrUe6dgPNtdQkP/3YJEhCN7NNypoXxfrlHiqFW
dGdbfB9MLC66EBboPj8UFucHVvPMij34ovhvyY/cv8k2RlkrhdY+yZnSLRoUD0f5
2ZczZO2G9yQPIt5QY0wZKPMJTwKjiQXvCIKKW1AmRCQ3PH72/Z9qtB96dtXe6n4J
UyYGwDMiu8h8GNF4aWYGXckFlAESkzKBvUnpjo3EdtCADZkegIHZpMUN2HgbJVsk
LPNcCk/m0Jy2FCOnXsav/PRBMUhQLsxWl7wW2uVCCU4dHkeRmULrTmS3L8HnY2fJ
2h7YtLNio9MIgEwmz+Q5oVpxU0vqW2SY6nuzOpDyDYnE5uXQpqRbNXTnUj7J0Z/p
u/2FhavpTepaOdMTZQ4UKN83p/139BsGHwzUsFk5qAL9A/2P7qcDD449QeDlgFBI
V57DHDKipUPcbJMP3eAjWY4AA3YqleWDmJGpzQ6p6GdwxGIs2qdl4OuR6gp67z60
+D3L+qI70V6zUFj6LT8w6GtWhT3nIsuEWLGjhwWndqDOXQOVeBWVwpazbIwqTxZ5
Ajum5FC5ZwALq+hGv45u2ghLnc/OiJNiFtD6Ibbb2NbpUg7xcOGCTb87bACO6Gkd
18Gmw7Uwc+GrEMmAqkXhSHq0PszxVOeliV7aFmcJPLcp9Dv9jNY2t4fga5FbhBRz
SXFpeJ3lc/pAk30/AD+J
=rNAy
-END PGP SIGNATURE-



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org