+3.5.6.0 Jul 01
+
+ - Emacs and TeX are no longer mandated by policy to be priority
+ standard packages
+ - Programs that access docs need to do so via /usr/share/doc, and
+ not via /usr/doc/ as was the policy previously
+ - Putting documentation in /usr/doc versus /usr/share/doc is now
+ a ``serious'' policy violation
+ - For web servers, one should not provide non-local access to the
+ /usr/share/doc heirarchy. If one can't provide access controls for
+ the //localhost/doc/ directory, then it is preferred that one
+ ask permission to expose that information during the install.
+
+3.5.5.0 May 01
+
+ - Manpages should not rely on header information to have
+ alternative manpage names available; it should only use
+ symlinks or .so pages to do this [13.1]
+ - [Clarified note in 3.5.3.0 upgrading checklist regarding
+ examples and templates: this refers only to those examples used
+ by scripts; see section 11.7.3 for the whole story]
+ - Included a new section 11.9.1 describing the use of
+ dpkg-statoverride; this does not have the weight of policy
+ - Clarify Standards-Version: you don't need to rebuild your
+ packages just to change the Standards-Version!
+ - Plugins are no longer bound by all the rules of shared
+ libraries [11.2]
+ - X Windows related things:
+ * Clarification of priority levels of X Window System related
+ packages [12.8.1]
+ * Rules for defining x-terminal-emulator improved [12.8.3]
+ * X Font policy rewritten: you must read this if you provide
+ fonts for the X Window System [12.8.5]
+ * Packages must not ship /usr/X11R6/lib/X11/app-defaults/ [12.8.6]
+ * X-related packages should usually use the regular FHS
+ locations; imake-using packages are exempted from this [12.8.7]
+ * OpenMotif linked binaries have the same rules as
+ OSF/Motif-linked ones [12.8.8]
+
+
+3.5.4.0 Apr 01
+
+ - The system-wide mail directory is now /var/mail, no longer
+ /var/spool/mail. Any packages accessing the mail spool should
+ access it via /var/mail and include a suitable Depends field;
+ details in [12.6]
+ - The perl policy is now part of Debian policy proper. Perl
+ programs and modules should follow the current Perl policy
+ [12.9; perl-policy]
+
+
+3.5.3.0 Apr 01
+
+ - Build-Depends arch syntax has been changed to be less
+ ambiguous. This should not affect any current packages [7.1]
+ - Examples and templates files for use by scripts should now live
+ in /usr/share/<package> or /usr/lib/<package>, with
+ symbolic links from /usr/share/doc//<package>/examples as
+ needed [11.7.3]
+
+
+3.5.2.0 Feb 01
+
+ - X app-defaults directory has moved from
+ /usr/X11R6/lib/X11/app-defaults to /etc/X11/app-defaults [12.8.6]
+
+
+3.5.1.0 Feb 01
+
+ - dpkg-shlibdeps now uses objdump, so shared libraries have to be
+ run through dpkg-shlibdeps as well as executables [9.1]
+
+
+3.5.0.0 Jan 01
+
+ - Font packages for the X Window System must now declare a
+ dependency on xutils (>= 4.0.2) [12.8.5]
+
+
+3.2.1.1 Jan 01
+
+ - Daemon startup scripts in /etc/init.d/ should not contain
+ modifiable parameters; these should be moved to a file in
+ /etc/default/; see [10.3.2] for details
+ - Files in /usr/share/doc must not be referenced by any
+ program. If such files are needed, they must be placed in
+ /usr/share/<package>/, and symbolic links created as required
+ in /usr/share/doc/<package>/ [13.3]
+ - Much of the packaging manual has now been imported into the
+ policy document
+
+
+3.2.1.0 Aug 00
+
+ - A package of priority standard or higher may provide two
+ binaries, one compiled with support for the X Window System,
+ and the other without [12.8.1]
+
+
+3.2.0.0 Aug 00
+
+ - By default executables should not be built with the debugging
+ option -g. Instead, it is recommended to support building the
+ package with debugging information optionally. Details in [11.1]
+ - Policy for packages where the upstream uses HTML changelog
+ files has been expanded. In short, a plain text changelog file
+ should always be generated for the upstream changes [13.8]
+ - Please note that the new release of the X window system (4.x)
+ shall probably need sweeping changes in policy
+ - Policy for packages providing the following X-based features
+ has been codified:
+ - X server (virtual package xserver) [12.8.2]
+ - X terminal emulator (virtual package x-terminal-emulator) [12.8.3]
+ - X window manager (virtual package x-window-manager, and
+ /usr/bin/x-window-manager alternative, with priority
+ calculation guidelines) [12.8.4]
+ - X fonts (this section has been written from scratch) [12.8.5]
+ - X application defaults [12.8.6]
+ - Policy for packages using the X Window System and FHS issues
+ has been clarified; see [12.8.7]
+ - No package may contain or make hard links to conffiles [11.7.3]
+ - Noted that newer dpkg versions do not require extreme care in
+ always creating the shared lib before the symlink, so the unpack
+ order be correct [9]
+
+
+3.1.1.0 Nov 99
+
+ - Correction to semantics of architecture lists in Build-Depends
+ etc. Should not affect many packages [7.1]
+
+
+3.1.0.0 Oct 99
+
+ - /usr/doc/<package> has to be a symlink pointing to
+ /usr/share/doc/<package>, to be maintained by postinst
+ and prerm scripts. Details are in [13.4]
+ - Introduced source dependencies (Build-Depends, etc.) [7.1, 7.6]
+ - /etc/rc.boot has been deprecated in favour of /etc/rcS.d.
+ (Packages should not be touching this directory, but should use
+ update-rc.d instead) [10.3.4]
+ - update-rc.d is now the *only* allowable way of accessing the
+ /etc/rc?.d/[SK]??* links. Any scripts which manipulate them
+ directly must be changed to use update-rc.d instead. (This is
+ because the file-rc package handles this information in an
+ incompatible way.) [10.3.3]
+ - Architecture-specific examples go in /usr/lib/<package>/examples
+ with symlinks from /usr/share/doc/<package>/examples/* or from
+ /usr/share/doc/<package>/examples itself [13.7]
+ - Updated FHS to a 2.1 draft; this reverts /var/state to
+ /var/lib [10.1.1]
+ - Added MIME sub-policy document [10.7; mime-policy]
+ - VISUAL is allowed as a (higher priority) alternative to EDITOR [12.4]
+ - Modified liblockfile description, which affects
+ mailbox-accessing programs. Please see the policy document for
+ details [12.6]
+ - If a package provides a changelog in HTML format, a text-only
+ version should also be included. (Such a version may be prepared
+ using lynx -dump -nolist.) [13.8]
+ - Description of how to handle version numbers based on dates
+ added [4.1]
+
+
+3.0.1.0 Jul 99
+
+ - Added the clarification that the .la files are essential for the
+ packages using libtool's libltdl library, in which case the
+ .la files must go in the run-time library package [11.2]
+
+