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

[Jonathan Nieder <jrnieder@gmail.com>]

Hi Charles,

Charles Plessy wrote:

> --- a/policy.sgml
> +++ b/policy.sgml
> @@ -7378,24 +7378,10 @@ Reloading <var>description</var> configuration...done.
>  	  The <package>mime-support</package> package provides the
>  	  <prgn>update-mime</prgn> program which allows packages to
>  	  register programs that can show, compose, edit or print
> -	  MIME types.
> +	  MIME types, using Dpkg triggers.

Nice, good to hear.

>                                         Packages registering such programs
> +	  should <em>not</em> depend on, recommend, or suggest
> +	  <prgn>mime-support</prgn>.

Carried over from before; still makes sense.

>  	</p>
> -
> -	<p>
> -	  Packages containing such programs must register them
> -	  with <prgn>update-mime</prgn> as documented in <manref
> -	  name="update-mime" section="8">. They should <em>not</em> depend
> -	  on, recommend, or suggest <prgn>mime-support</prgn>. Instead,
> -	  they should just put something like the following in the
> -	  <tt>postinst</tt> and <tt>postrm</tt> scripts:

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

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

in case the interest pattern changes?  Or should I use the old-fashioned

	if type update-mime >/dev/null 2>&1; then
		update-mime
	fi

?

Aside from that detail, looks good.

Thanks,
Jonathan