X-Git-Url: https://git.donarmstrong.com/?p=debian%2Fdebian-policy.git;a=blobdiff_plain;f=policy.sgml;h=404dc7373f80cdc20bf793e064d7163e3885518f;hp=1743552e0f16e5d104fc99c8b7ed6221b9b9dee4;hb=HEAD;hpb=ba679bff76f5b9152f43d5bc901b9b3aad257479
diff --git a/policy.sgml b/policy.sgml
index 1743552..404dc73 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -229,9 +229,8 @@
The maintainer name and email address used in the changelog
- should be the details of the person uploading this
- version. They are not necessarily those of the
- usual package maintainer.
+ For packages in the main archive, no required targets + may attempt network access. +
The targets are as follows:
@@ -2367,8 +2373,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
Empty field values are only permitted in source package control files
+ (
A paragraph must not contain more than one instance of a
particular field name.
@@ -2700,6 +2707,7 @@ Package: libc6
file. These tools are responsible for removing the line
breaks from such fields when using fields from
@@ -3674,7 +3682,7 @@ Files:
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 +6926,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
@@ -6959,8 +6981,18 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1)
+ The requirement for C and C++ headers files to be
+ accessible through the search path
+
@@ -7029,6 +7061,21 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1) kernel information.
+ The
+ The requirement for
On GNU/Hurd systems, the following additional @@ -7309,6 +7356,35 @@ rmdir /usr/local/share/emacs 2>/dev/null || true
+ This value must not be used, because it was + the error return sentinel value when uid_t + was 16 bits. +
+
+ Dynamically allocated user accounts. By
+ default
+ (uid_t)(-2) == (gid_t)(-2) must not be + used, because it is used as the anonymous, unauthenticated + user by some NFS implementations. +
+
(uid_t)(-1) == (gid_t)(-1) must
@@ -8054,75 +8130,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.
-
-
- 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
-
+ Menu entries should follow the current menu policy.
+ 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
@@ -8945,6 +8927,7 @@ fname () {
would point to
@@ -9802,15 +9785,16 @@ done
Cgi-bin executable files are installed in the
directory
- Any additional documentation that comes with the package may
- be installed at the discretion of the package maintainer.
- Plain text documentation should be installed in the directory
-
- If a package comes with large amounts of documentation which - many users of the package will not require you should create - a separate binary package to contain it, so that it does not - take up disk space on the machines of users who do not need - or want it installed.
+ Plain text documentation should be compressed with gzip + -9 unless it is small. +
- It is often a good idea to put text information files
- (
+ Additional documentation included in the package should be
+ installed under
+ Any separate package providing documentation must still install
+ standard documentation files in its
+ own
Packages must not require the existence of any files in
@@ -10736,18 +10752,6 @@ END-INFO-DIR-ENTRY
- -
- Former Debian releases placed all additional documentation
- in
- If your package comes with extensive documentation in a
+ If the package comes with extensive documentation in a
markup format that can be converted to various other formats
you should if possible ship HTML versions in a binary
- package, in the directory
-