X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=policy.sgml;h=1743552e0f16e5d104fc99c8b7ed6221b9b9dee4;hb=f545dfd88c291812520adee2147723a47e16f220;hp=953d5d258069f7947d29140249a6de43cf73a831;hpb=8fcdad7dce1d1be17ae4fdb8ec591b53ce688199;p=debian%2Fdebian-policy.git
diff --git a/policy.sgml b/policy.sgml
index 953d5d2..1743552 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -2542,7 +2542,7 @@ endif
composed of US-ASCII characters excluding control characters,
space, and colon (i.e., characters in the ranges 33-57 and
59-126, inclusive). Field names must not begin with the comment
- character, #.
+ character, #, nor with the hyphen character, -.
@@ -2759,6 +2759,7 @@ Package: libc6
- Uploaders
- Homepage
- Vcs-Browser, Vcs-Git, et al.
+ - Dgit
- Standards-Version (recommended)
- Build-Depends et al
- Package-List (recommended)
@@ -3840,6 +3841,26 @@ Checksums-Sha256:
this value is assumed for paragraphs lacking this field.
+
+
+ Dgit
+
+
+ Folded field containing a single git commit hash, presented in
+ full, followed optionally by whitespace and other data to be
+ defined in future extensions.
+
+
+
+ Declares that the source package corresponds exactly to a
+ referenced commit in a Git repository available at the canonical
+ location called dgit-repos, used by dgit, a
+ bidirectional gateway between the Debian archive and Git. The
+ commit is reachable from at least one reference whose name matches
+ refs/dgit/*. See the manual page of dgit for
+ further details.
+
+
@@ -7000,15 +7021,14 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1)
stable release of Debian supports /run.
- -
-
- The following directories in the root filesystem are
- additionally allowed: /sys and
- /selinux. These directories
- are used as mount points to mount virtual filesystems
- to get access to kernel information.
-
-
+ -
+
+ The /sys directory in the root filesystem is
+ additionally allowed. This directory is used as
+ mount point to mount virtual filesystems to get access to
+ kernel information.
+
+
-
On GNU/Hurd systems, the following additional
@@ -8034,38 +8054,75 @@ Reloading description configuration...done.
Menus
- The Debian menu package provides a standard
- interface between packages providing applications and
- menu programs (either X window managers or
- text-based menu programs such as pdmenu).
+ Packages shipping applications that comply with minimal requirements
+ described below for integration with desktop environments should
+ register these applications in the desktop menu, following the
+ FreeDesktop standard, using text files called
+ desktop entries. Their format is described in the
+ Desktop Entry Specification at
+
+ and complementary information can be found in the
+ Desktop Menu Specification at
+ .
- All packages that provide applications that need not be
- passed any special command line arguments for normal
- operation should register a menu entry for those
- applications, so that users of the menu package
- will automatically get menu entries in their window
- managers, as well in shells like pdmenu.
+ The desktop entry files are installed by the packages in the
+ directory /usr/share/applications and the FreeDesktop
+ menus are refreshed using dpkg triggers. It is therefore
+ not necessary to depend on packages providing FreeDesktop menu
+ systems.
- Menu entries should follow the current menu policy.
+ Entries displayed in the FreeDesktop menu should conform to the
+ following minima for relevance and visual integration.
+
+
+ -
+ Unless hidden by default, the desktop entry must point to a PNG
+ or SVG icon with a transparent background, providing at least
+ the 22×22 size, and preferably up to 64×64. The icon
+ should be neutral enough to integrate well with the default icon
+ themes. It is encouraged to ship the icon in the default
+ hicolor icon theme directories, or to use an existing
+ icon from the hicolor theme.
+
+
+ -
+ If the menu entry is not useful in the general case as a
+ standalone application, the desktop entry should set the
+ NoDisplay key to true, so that it can be
+ configured to be displayed only by those who need it.
+
+
+ -
+ In doubt, the package maintainer should coordinate with the
+ maintainers of menu implementations through the
+ debian-desktop mailing list in order to avoid problems
+ with categories or bad interactions with other icons. Especially
+ for packages which are part of installation tasks, the contents
+ of the NotShowIn/OnlyShowIn keys should be
+ validated by the maintainers of the relevant environments.
+
+
- The menu policy can be found in the menu-policy
- files in the debian-policy package.
- It is also available from the Debian web mirrors at
- .
+ Since the FreeDesktop menu is a cross-distribution standard, the
+ desktop entries written for Debian should be forwarded upstream,
+ where they will benefit to other users and are more likely to
+ receive extra contributions such as translations.
-
- Please also refer to the Debian Menu System
- documentation that comes with the menu
- package for information about how to register your
- applications.
+
+ Packages can, to be compatible with Debian additions to some window
+ managers that do not support the FreeDesktop standard, also provide a
+ Debian menu file, following the Debian menu policy,
+ which can be found in the menu-policy files in the
+ debian-policy package. It is also available from the Debian
+ web mirrors at .
@@ -8073,42 +8130,109 @@ Reloading description configuration...done.
Multimedia handlers
- MIME (Multipurpose Internet Mail Extensions, RFCs 2045-2049)
- is a mechanism for encoding files and data streams and
- providing meta-information about them, in particular their
- type (e.g. audio or video) and format (e.g. PNG, HTML,
- MP3).
+ Media types (formerly known as MIME types, Multipurpose Internet Mail
+ Extensions, RFCs 2045-2049) is a mechanism for encoding files and
+ data streams and providing meta-information about them, in particular
+ their type and format (e.g. image/png, text/html,
+ audio/ogg).
- Registration of MIME type handlers allows programs like mail
+ Registration of media type handlers allows programs like mail
user agents and web browsers to invoke these handlers to
- view, edit or display MIME types they don't support directly.
+ view, edit or display media types they don't support directly.
- Packages which provide programs to view/show/play, compose, edit or
- print MIME types should register them as such by placing a file in
- format (RFC 1524) in the directory
- /usr/lib/mime/packages/. The file name should be the
- binary package's name.
+ There are two overlapping systems to associate media types to programs
+ which can handle them. The mailcap system is found on a
+ large number of Unix systems. The FreeDesktop system is
+ aimed at Desktop environments. In Debian, FreeDesktop entries are
+ automatically translated in mailcap entries, therefore packages
+ already using desktop entries should not use the mailcap system
+ directly.
-
- The mime-support package provides the
- update-mime program, which integrates these
- registrations in the /etc/mailcap file, using dpkg
- triggers
- Creating, modifying or removing a file in
- /usr/lib/mime/packages/ using maintainer scripts will
- not activate the trigger. In that case, it can be done by calling
- dpkg-trigger --no-await /usr/lib/mime/packages from
- the maintainer script after creating, modifying, or removing
- the file.
- .
- Packages using this facility should not depend on,
- recommend, or suggest mime-support.
-
+
+ Registration of media type handlers with desktop entries
+
+
+ Packages shipping an application able to view, edit or point to
+ files of a given media type, or open links with a given URI scheme,
+ should list it in the MimeType key of the application's
+ . For URI schemes,
+ the relevant MIME types are x-scheme-handler/* (e.g.
+ x-scheme-handler/https).
+
+
+
+
+ Registration of media type handlers with mailcap entries
+
+
+ Packages that are not using desktop entries for registration should
+ install a file in 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 integrates these
+ registrations in the /etc/mailcap file, using dpkg
+ triggers
+ Creating, modifying or removing a file in
+ /usr/lib/mime/packages/ using maintainer scripts will
+ not activate the trigger. In that case, it can be done by calling
+ dpkg-trigger --no-await /usr/lib/mime/packages from
+ the maintainer script after creating, modifying, or removing
+ the file.
+ .
+
+
+ Packages installing desktop entries should not install mailcap
+ entries for the same program, because the
+ mime-support package already reads desktop
+ entries.
+
+
+
+ Packages using these facilities should not depend on,
+ recommend, or suggest mime-support.
+
+
+
+
+ Providing media types to files
+
+
+ The media type of a file is discovered by inspecting the file's
+ extension or its pattern, and
+ interrogating a database associating them with media types.
+
+
+
+ To support new associations between media types and files, their
+ characteristic file extensions and magic patterns should be
+ registered to the IANA (Internet Assigned Numbers Authority). See
+ 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 and file
+ packages. If registration and propagation can not be waited for,
+ support can be asked to the maintainers of the packages mentioned
+ above.
+
+
+
+ For files that are produced and read by a single application, it
+ is also possible to declare this association to the
+ Shared MIME Info system by installing in the directory
+ /usr/share/mime/packages a file in the XML format
+ specified at .
+
+
@@ -8853,7 +8977,9 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
- A symbolic link pointing to a compressed file should always
+ A symbolic link pointing to a compressed file (in the sense
+ that it is meant to be uncompressed with unzip
+ or zless etc.) should always
have the same file extension as the referenced file. (For
example, if a file foo.gz is referenced by a
symbolic link, the filename of the link has to end with
@@ -8987,8 +9113,10 @@ ln -fs ../sbin/sendmail debian/tmp/usr/bin/runq
package is purged.
- Obsolete configuration files without local changes may be
- removed by the package during upgrade.
+ Obsolete configuration files without local changes should be
+ removed by the package during upgrade.
+ The dpkg-maintscript-helper tool, available from the
+ dpkg package, can help for this task.
@@ -9471,6 +9599,23 @@ done
+
+
+ File names
+
+
+ The name of the files installed by binary packages in the system PATH
+ (namely /bin, /sbin, /usr/bin,
+ /usr/sbin and /usr/games) must be encoded in
+ ASCII.
+
+
+
+ The name of the files and directories installed by binary packages
+ outside the system PATH must be encoded in UTF-8 and should be
+ restricted to ASCII when it is possible to do so.
+
+