Bug#661816: debian-policy: Do not call update-mime directly, since it is triggered by Dpkg.

[Jonathan Nieder <jrnieder@gmail.com>]

Hi,

Charles Plessy wrote:
> Le Thu, Mar 01, 2012 at 08:42:57AM -0600, Jonathan Nieder a écrit :

>> If my package generates its mailcap file on the fly in postinst, what command
>> should it run to make sure it gets used?  Is
>>
>> 	dpkg-trigger --no-await --by-package=<this package> /usr/lib/mime/packages
>>
>> guaranteed to continue to work in the future?  Do I need to do
[...]
> this look like quite a corner case: I could not find the string "mailcap" in
> the maintainer pre and post-installation scripts available in the Lintian lab.
>
> I think that in these rare cases, a direct call to update-mime in postinst
> would be fine.

dpkg-trigger was fixed to make

	dpkg-trigger --no-await --by-package=<me> /usr/lib/mime/packages

do the right thing in version 1.16.4 (phew).  So my preference would be to
document that packages wanting to manually make sure their addition to
the mime database is reflected should trigger that path.

Providing dynamically generated mime info would presumably require
installing a symlink at /usr/lib/mime/packages/<me>, anyway, so it
doesn't worry me too much.