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=63b7f87c44284a764154b18c8d440ce5e4c2e8f6;hp=f1130c201501d35ba885d879ae58665001d8cb50;hb=24edeec3ea3aef827fc6c23b59bafec1f5343593;hpb=8a77d09ebb4f5b985db6da174892a3a66d5aa272
diff --git a/best-pkging-practices.dbk b/best-pkging-practices.dbk
index f1130c2..63b7f87 100644
--- a/best-pkging-practices.dbk
+++ b/best-pkging-practices.dbk
@@ -142,6 +142,8 @@ the same software but with different configuration options. The vim source package is an example of how to manage
this using an hand-crafted debian/rules file.
+
@@ -318,6 +320,10 @@ implementation? more features? different features? Why should I choose this
package.
+
@@ -601,6 +607,17 @@ NEWS.Debian file in your package. No news is good news!
+
+
Best practices for maintainer scripts
@@ -1303,6 +1320,15 @@ easier, for instance, to keep URLs up to date across multiple files.
Common packaging situations
+
+
+
Architecture-independent data
@@ -1613,6 +1660,7 @@ come from the upstream author(s), or whose contents has been changed by you.
would lead to the source failing to build without assistance from the Debian
diff, it might be appropriate to instead edit the files, omitting only the
non-free parts of them, and/or explain the situation in a README.Debian-source
+
file in the root of the source tree. But in that case please also urge the
upstream author to make the non-free components easier seperable from the rest
of the source.