X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=policy.sgml;h=4855506e6105556bc6db756e712ed4f849dcbc68;hb=3c725b9d2af39ac3a7e24b7d9eb374a48c5b6893;hp=1743552e0f16e5d104fc99c8b7ed6221b9b9dee4;hpb=f545dfd88c291812520adee2147723a47e16f220;p=debian%2Fdebian-policy.git
diff --git a/policy.sgml b/policy.sgml
index 1743552..4855506 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -2367,8 +2367,7 @@ endif
This is an optional, recommended configuration file for the
uscan utility which defines how to automatically scan
ftp or http sites for newly available updates of the
- package. This is used
- by
The special value byhand for the section in a .changes file indicates that the file in question - is not an ordinary package file and must by installed by + is not an ordinary package file and must be installed by hand by the distribution maintainers. If the section is byhand the priority should be -.
@@ -6918,6 +6917,20 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1) exceptions to the FHS apply:
+ The FHS requirement that architecture-independent
+ application-specific static files be located in
+
The optional rules related to user specific @@ -6963,6 +6976,17 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1) multiarch.
+
+ The requirement for C and C++ headers files to be
+ accessible through the search path
+
Applications may also use a single subdirectory under
+ The requirement for
On GNU/Hurd systems, the following additional
@@ -8054,75 +8088,38 @@ Reloading description configuration...done.
- 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
-
- The desktop entry files are installed by the packages in the
- directory
- Entries displayed in the FreeDesktop menu should conform to the
- following minima for relevance and visual integration.
-
-
-
+ Menu entries should follow the current menu policy.
- 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.
+ 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
+
- 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
+ Please also refer to the Debian Menu System
+ documentation that comes with the
- 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). + 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).
- Registration of media type handlers allows programs like mail + Registration of MIME type handlers allows programs like mail user agents and web browsers to invoke these handlers to - view, edit or display media types they don't support directly. + view, edit or display MIME types they don't support directly.
- 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.
+ Packages which provide programs to view/show/play, compose, edit or
+ print MIME types should register them as such by placing a file in
+
- 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
-
- Packages that are not using desktop entries for registration should
- install a file in
- The
- Packages installing desktop entries should not install mailcap
- entries for the same program, because the
-
- Packages using these facilities should not depend on,
- recommend, or suggest
- The media type of a file is discovered by inspecting the file's
- extension or its
- 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
-
- 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
-
+ The
+ Binary executables must not be statically linked with the GNU C + library, since this prevents the binary from benefiting from + fixes and improvements to the C library without being rebuilt + and complicates security updates. This requirement may be + relaxed for binary executables whose intended purpose is to + diagnose and fix the system in situations where the GNU C + library may not be usable (such as system recovery shells or + utilities like ldconfig) or for binary executables where the + security benefits of static linking outweigh the drawbacks. +
By default, when a package is being built, any binaries
created should include debugging information, as well as
@@ -9802,15 +9742,16 @@ done
Cgi-bin executable files are installed in the
directory