On 2014-09-14 13:28, Yann Dirson wrote:
On Sun, Sep 14, 2014 at 10:12:41AM +0200, Pino Toscano wrote:
Hi,
first of all, the behaviour of update-mime-database is correct: it
deletes files in *generated* directories.
Yes, the various application, audio, text, subdirectories under
/usr/share/mime are business of update-mime-database, where it
places
the XML mimetypes generated from the XML definitions in
/usr/share/mime/packages. It is exactly in this directory where
applications should install XML definitions of mime types to have
them
registered in the XDG mime type system.
Installing stuff directly to e.g. /usr/share/mime/text is like
installing to, say, /var/cache (i.e., you shouldn't).
Furthermore, qgo is installing wrong things, and I will send the
proper explanation and fix to #749582.
This is not a bug in shared-mime-info, hence closing.
Ah, that's interesting. But then:
* why are those directories in /usr/ and not in /var/ in the first
place ? Isn't this part of the shared-mime-info spec against the
spirit of the FHS ?
Possibly, although changing at this point is not exactly an easy
task.
* if it is deemed the right place for generated files, then we
surely want a lintian check to spot the problem early
Feel free to file a wishlist bug for lintian.
* the update-mime-database manpage is quite terse, and does not
explain that different parts of MIME-DIR have different roles.
It is awkward to have to read the spec to get such important
information
I guess you are referring to the update-mime-database man page, right?
This seems just specific to the tool itself, so IMHO what it lacks is
pointers to the specifications.
Another option would be having the specifications themselves as man
page.
--
Pino Toscano
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
