Sec "Multiple binary packages": fix awkward wording about vim source

package; closes: #187143; some notes and FIXMES which need to be dealt with

git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@2232 313b444b-1b9f-4f58-a734-7bb04f332e8d

diff --git a/developers-reference.sgml b/developers-reference.sgml
index 01a10be930d4ed4c1dc98b464d0b2eee0d42d6d3..ab5b26f621930ec37d376aadffc170d095cc06e4 100644 (file)
--- a/developers-reference.sgml
+++ b/developers-reference.sgml
@@ -6,7 +6,7 @@
   <!entity % commondata  SYSTEM "common.ent" > %commondata;
 
   <!-- CVS revision of this document -->
-  <!entity cvs-rev "$Revision: 1.196 $">
+  <!entity cvs-rev "$Revision: 1.197 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -1217,6 +1217,10 @@ package for the alpha architecture. Each time the package has been
 recompiled on most of the architectures.
 
     <sect id="pkg-tracking-system">The Package Tracking System
+<!-- FIXME: talk about 
+http://qa.debian.org/developer.php?login=aph@debian.org
+http://packages.qa.debian.org/
+http://packages.qa.debian.org/pkgname -->
        <p>
 The Package Tracking System (PTS) is basically a tool to track by mail
 the activity of a source package. You just have to subscribe
@@ -3086,22 +3090,22 @@ documentation and examples (in <file>/usr/share/doc/dpatch</file>).
        <sect1 id="multiple-binary">Multiple binary packages
        <p>
 A single source package will often build several binary packages,
-either to provide several flavors of the same software (examples are
-the <package>vim-*</package> packages) or to make several small
+either to provide several flavors of the same software (e.g.,
+the <package>vim</package> source package) or to make several small
 packages instead of a big one (e.g., if the user can install only the
 subset she needs, and thus save some disk space).
        <p>
 The second case can be easily managed in <file>debian/rules</file>.
 You just need to move the appropriate files from the build directory
 into the package's temporary trees.  You can do this using
-<prgn>install</prgn> (vanilla approach) or <prgn>dh_install</prgn>
-(from <package>debhelper</package>).  Be sure to check the different
+<prgn>install</prgn> or <prgn>dh_install</prgn>
+from <package>debhelper</package>.  Be sure to check the different
 permutations of the various packages, ensuring that you have the
 inter-package dependencies set right in <file>debian/control</file>.
        <p>
 The first case is a bit more difficult since it involves multiple
-recompiles of the same software but with different configure
-options. The <package>vim</package> is an example of how to manage
+recompiles of the same software but with different configuration
+options. The <package>vim</package> source package is an example of how to manage
 this using an hand-crafted <file>debian/rules</file> file.
 
 <!-- &FIXME; Find a good debhelper example with multiple configure/make
@@ -4434,6 +4438,7 @@ it.</p>
 questionable:
   dbs (referred to above)
   dpatch (referred to above)
+  debarchiver
   ucf
   dpkg-awk
   grep-dctrl