Control: found -1 2.3.7-1 Control: tags = upstream wontfix On Wed, 2015-06-10 at 12:26 +0100, David King wrote: > On 2015-06-10 11:10, James Cowgill <james...@cowgill.org.uk> wrote: > > This bug has been reported a few times upstream. > > … > > The argument against changing it was that easytag can infact handle the > > inode/directory MIME type properly so it should be allowed to have it > > in it's MimeTypes list. > > > > On balance (due to the issues it causes) I would probably lean towards > > removing it, which I see has already been done in git. > > The MIME type is still present in the desktop file (and in the Nautilus > extension for the master branch) in git.
I was referring to the packaging repo and this commit: https://anonscm.debian.org/cgit/pkg-multimedia/easytag.git/commit/?id=06db31be783e83aa146605260306a33fe5a9b8c3 > > David? > > It is not really a problem of EasyTAG that installing a desktop file, > with a valid list of accepted MIME types, causes a different part of the > system to adjust its associations. There is no defined way to adjust > MIME type associations across all desktop environments, and each > environment handles this differently. Modern GNOME versions simply > ignore the inode/directory MIME association on anything that is not > Nautilus. The more I read about this situation affecting other projects, the more I think David is right. All easytag is doing is following the freedesktop spec and since easytag can handle directories, it should have the directory mime type registered to it. This should either be fixed in gnome-open or the spec should be updated to allow apps to specify priorities. Other projects which kept this mime type: https://bugs.kde.org/show_bug.cgi?id=309204 http://redmine.audacious-media-player.org/issues/102 Other projects which removed it: https://code.google.com/p/rawtherapee/issues/detail?id=1398 Thanks, James
signature.asc
Description: This is a digitally signed message part