Author: jdg
Date: 2001/08/22 23:26:45
* Correct syntax error (sentence fragment missing) regarding the ldd
-> objdump transition
* Correct 'commment' -> 'comment' speling error
* Add section refs in checklist
* Start new section in changelog
git-archimport-id: srivasta@debian.org--etch/debian-policy--devel--3.0--patch-134
+debian-policy (3.5.6.1) unstable; urgency=low
+
+ *
+
+ --
+
debian-policy (3.5.6.0) unstable; urgency=low
* Change footnote about urgency values to the now-current list: low,
debian-policy (3.5.6.0) unstable; urgency=low
* Change footnote about urgency values to the now-current list: low,
* The old packaging manual is included in the policy document as an
informative appendix. It is not part of Debian Technical Policy, and
its presence is a temporary measure until dpkg documentation includes
* The old packaging manual is included in the policy document as an
informative appendix. It is not part of Debian Technical Policy, and
its presence is a temporary measure until dpkg documentation includes
- ther information provided. closes: Bug#105535
+ the information provided. closes: Bug#105535
* Added information about optional blank lines in the chagelog format.
closes: Bug#105538
* Added information about optional blank lines in the chagelog format.
closes: Bug#105538
These packages provide a reasonably small but not too
limited character-mode system. This is what will be
installed by default if the user doesn't select anything
These packages provide a reasonably small but not too
limited character-mode system. This is what will be
installed by default if the user doesn't select anything
- else. It doesn't include many large applications.
- .</p>
+ else. It doesn't include many large applications.</p>
</item>
<tag><tt>optional</tt></tag>
<item>
</item>
<tag><tt>optional</tt></tag>
<item>
<p>
In the past, the shared libraries linked to were
determined by calling <prgn>ldd</prgn>, but now
<p>
In the past, the shared libraries linked to were
determined by calling <prgn>ldd</prgn>, but now
- <prgn>objdump</prgn> to do this. The only change this
- makes to package building is that
+ <prgn>objdump</prgn> is used to do this. The only
+ change this makes to package building is that
<prgn>dpkg-shlibdeps</prgn> must also be run on shared
libraries, whereas in the past this was unnecessary.
The rest of this footnote explains the advantage that
<prgn>dpkg-shlibdeps</prgn> must also be run on shared
libraries, whereas in the past this was unnecessary.
The rest of this footnote explains the advantage that
<p>
Each <tt>shlibs</tt> file has the same format. Lines
<p>
Each <tt>shlibs</tt> file has the same format. Lines
- beginning with <tt>#</tt> are considered to be commments and
+ beginning with <tt>#</tt> are considered to be comments and
are ignored. Each line is of the form:
<example compact="compact">
<var>library-name</var> <var>soname-version-number</var> <var>dependencies ...</var>
are ignored. Each line is of the form:
<example compact="compact">
<var>library-name</var> <var>soname-version-number</var> <var>dependencies ...</var>
3.5.6.0 Jul 01
- Emacs and TeX are no longer mandated by policy to be priority
3.5.6.0 Jul 01
- Emacs and TeX are no longer mandated by policy to be priority
+ standard packages [2.2]
- Programs that access docs need to do so via /usr/share/doc, and
- Programs that access docs need to do so via /usr/share/doc, and
- not via /usr/doc/ as was the policy previously
+ not via /usr/doc/ as was the policy previously [12.5]
- Putting documentation in /usr/doc versus /usr/share/doc is now
- Putting documentation in /usr/doc versus /usr/share/doc is now
- a ``serious'' policy violation
+ 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
- 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.
+ ask permission to expose that information during the install [12.5]
+