Bug#1008480: debian-policy: The mime-support package was split into media-types and mailcap
Package: debian-policy
Version: 4.6.0.1
Severity: normal
X-Debbugs-Cc: plessy@debian.org
Hi Russ and Sean,
it is a long time I have not posted here!
In the previous release cycle, I have split the mime-support into the
media-types and the mailcap packages.
The patch below updates the Policy to reflect that.
Have a nice Sunday,
-- Charles
diff --git a/policy/ch-opersys.rst b/policy/ch-opersys.rst
index 83b71b1..72923f9 100644
--- a/policy/ch-opersys.rst
+++ b/policy/ch-opersys.rst
@@ -796,16 +796,16 @@ install a file in :manpage:`mailcap(5)` format (RFC 1524) in the directory
``/usr/lib/mime/packages/``. The file name should be the binary package's
name.
-The mime-support package provides the ``update-mime`` program, which
+The mailcap package provides the ``update-mime`` program, which
integrates these registrations in the ``/etc/mailcap`` file, using dpkg
triggers. [#]_
Packages installing desktop entries should not install mailcap entries
-for the same program, because the mime-support package already reads
+for the same program, because the mailcap package already reads
desktop entries.
Packages using these facilities *should not* depend on, recommend, or
-suggest ``mime-support``.
+suggest ``mailcap``.
.. _s-file-media-type:
@@ -821,7 +821,7 @@ characteristic file extensions and magic patterns should be registered
to the IANA (Internet Assigned Numbers Authority). See
https://www.iana.org/assignments/media-types and RFC 6838 for details.
This information will then propagate to the systems discovering file
-media types in Debian, provided by the shared-mime-info, mime-support
+media types in Debian, provided by the shared-mime-info, media-types
and file packages. If registration and propagation can not be waited
for, support can be asked to the maintainers of the packages mentioned
above.
Reply to: