On 06/16/2015 01:01 PM, James Cowgill wrote: > 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.
i can follow david's arguing and agree that it is not a bug in easytag (upstream). however, i don't think that the problem is with gnome-open or the freedesktop specs. installing the easytag package adds an entry to my /etc/mailcap file, that registers easytag as a program to "display non-text [directories] at the local site" (from mailcap(5), with a clarification by me in brackets). now i think that this is the main problem: easytag's desktop files declares that it *can* handle directories. (i guess the use case is that in your favourite filesystem browser you ought to be able to right-click on a directory and be presented with a list of applications that could handle that directory; having easytag in that list makes total sense to me). however, this declaration somehow makes the package installation process believe that it *should* handle directories (which is plain wrong), by adding an entry to /etc/mailcap. most likely the problem is with the packaging (not necessarily the easytag package per se, but maybe the tools used). according to update-mime(8), it *is* possible to add priorities to mime-types (for exactly the kind of problem we are facing). right now, easytag does not do anything special to register the mime-type handler, so it seems that the packaging should actively lower the priority. gfmadr IOhannes
signature.asc
Description: OpenPGP digital signature