Bug 24669 - Mime type for /usr/share/mime/packages/* files
Summary: Mime type for /usr/share/mime/packages/* files
Status: RESOLVED WONTFIX
Alias: None
Product: shared-mime-info
Classification: Unclassified
Component: freedesktop.org.xml (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) All
: medium enhancement
Assignee: Jonathan Blandford
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-21 18:42 UTC by Matt McCutchen
Modified: 2010-01-28 09:18 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Draft MIME info for shared-mime-info files (406 bytes, text/xml)
2009-10-21 18:42 UTC, Matt McCutchen
Details
MIME info v2: add lower glob weight and comments (1.15 KB, text/plain)
2009-10-30 21:17 UTC, Matt McCutchen
Details

Description Matt McCutchen 2009-10-21 18:42:13 UTC
Created attachment 30608 [details]
Draft MIME info for shared-mime-info files

It might be nice to define a MIME type to describe shared-mime-info files themselves (i.e., /usr/share/mime/packages* ).  It's not important, but I drafted some MIME info for my own use and thought I would share it.
Comment 1 Matt McCutchen 2009-10-30 21:17:32 UTC
Created attachment 30861 [details]
MIME info v2: add lower glob weight and comments

I realized that the *.xml glob for application/x-shared-mime-info needs to have lower weight than the one for application/xml to make sure that application/xml is reliably favored unless the application/x-shared-mime-info magic matches.  Glib had some trouble with this setup.  The attachment adds the lower weight, a comments about glib, and a comment about the failure to match freedesktop.org.xml itself due to the long DTD.
Comment 2 Bastien Nocera 2010-01-28 09:18:23 UTC
I don't think this is interesting as a feature. Those files are simple XML files, with no interest whatsoever to any application in their raw forms.

If we had an editor to create those, I might change my mind...


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.