X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=best-pkging-practices.dbk;h=bbcf706eb2321812c0540149b18e46be63a96b15;hp=08a425da6a71ab90514be5200136b5639d7acea5;hb=7ec99366f11ebbba12919979d3ada164594b4674;hpb=81c0e6409c7dfef4af519821a76dbfadb7dd4758
diff --git a/best-pkging-practices.dbk b/best-pkging-practices.dbk
index 08a425d..bbcf706 100644
--- a/best-pkging-practices.dbk
+++ b/best-pkging-practices.dbk
@@ -1117,7 +1117,7 @@ description is in the Description: line of the template.
The short description should be kept short (50 characters or so) so that it may
-be accomodated by most debconf interfaces. Keeping it short also helps
+be accommodated by most debconf interfaces. Keeping it short also helps
translators, as usually translations tend to end up being longer than the
original.
@@ -1224,7 +1224,7 @@ strongly discouraged.
The short description should be phrased in the form of a question which should
be kept short and should generally end with a question mark. Terse writing
style is permitted and even encouraged if the question is rather long (remember
-that translations are often longer than original versions)
+that translations are often longer than original versions).
@@ -1350,7 +1350,7 @@ translated.
If the default value may vary depending on language/country (for instance the
default value for a language choice), consider using the special _Default
type documented in po-debconf
-7 ).
+7 .
@@ -1362,7 +1362,7 @@ type documented in po-debconf
Internationalization
This section contains global information for developers to make translators'
-life easier. More information for translators and developers interrested
+life easier. More information for translators and developers interested
in internationalization are available in the Internationalisation and localisation in Debian
documentation.
@@ -1670,10 +1670,17 @@ your short description. If you are looking for examples, just run:
apt-cache search .|grep dummy or
apt-cache search .|grep transitional.
+
+Also, it is recommended to adjust its section to
+oldlibs
+and its priority to
+extra
+in order to ease deborphan's job.
+
-Best practices for <filename>.orig.tar.{gz,bz2,lzma}</filename> files
+Best practices for <filename>.orig.tar.{gz,bz2,xz}</filename> files
There are two kinds of original source tarballs: Pristine source and repackaged
upstream source.
@@ -1682,7 +1689,7 @@ upstream source.
Pristine source
The defining characteristic of a pristine source tarball is that the
-.orig.tar.{gz,bz2,lzma} file is byte-for-byte identical to a tarball officially
+.orig.tar.{gz,bz2,xz} file is byte-for-byte identical to a tarball officially
distributed by the upstream author. We cannot prevent
upstream authors from changing the tarball they distribute without also
incrementing the version number, so there can be no guarantee that a pristine
@@ -1692,7 +1699,7 @@ identical to something that upstream once did distribute.
If a difference arises later (say, if upstream notices that he wasn't using
maximal compression in his original distribution and then
re-gzips it), that's just too bad. Since there is no good
-way to upload a new .orig.tar.{gz,bz2,lzma} for the same version, there is not even any
+way to upload a new .orig.tar.{gz,bz2,xz} for the same version, there is not even any
point in treating this situation as a bug. This makes it
possible to use checksums to easily verify that all changes between Debian's
version and upstream's are contained in the Debian diff. Also, if the original
@@ -1746,17 +1753,17 @@ gzipped tar at all, or if upstream's tarball contains non-DFSG-free material
that you must remove before uploading.
-In these cases the developer must construct a suitable .orig.tar.{gz,bz2,lzma}
+In these cases the developer must construct a suitable .orig.tar.{gz,bz2,xz}
file himself. We refer to such a tarball as a repackaged upstream
source. Note that a repackaged upstream source is different from a
Debian-native package. A repackaged source still comes with Debian-specific
-changes in a separate .diff.gz or .debian.tar.{gz,bz2,lzma}
+changes in a separate .diff.gz or .debian.tar.{gz,bz2,xz}
and still has a version number composed of upstream-version and
debian-version.
There may be cases where it is desirable to repackage the source even though
-upstream distributes a .tar.{gz,bz2,lzma} that could in principle be
+upstream distributes a .tar.{gz,bz2,xz} that could in principle be
used in its pristine form. The most obvious is if
significant space savings can be achieved by recompressing
the tar archive or by removing genuinely useless cruft from the upstream
@@ -1764,7 +1771,7 @@ archive. Use your own discretion here, but be prepared to defend your decision
if you repackage source that could have been pristine.
-A repackaged .orig.tar.{gz,bz2,lzma}
+A repackaged .orig.tar.{gz,bz2,xz}
@@ -1897,6 +1904,33 @@ debugging symbols for, and this dependency should be versioned. For example:
Depends: libfoo (= ${binary:Version})
+