From: aph <aph@313b444b-1b9f-4f58-a734-7bb04f332e8d>
Date: Sat, 22 Feb 2003 21:05:13 +0000 (+0000)
Subject: Sec bpp-archindepdata: editorial changes
X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=commitdiff_plain;h=a5865811bf0e5c563bedba48dfb0cbb75ebe4924;p=developers-reference.git

Sec bpp-archindepdata: editorial changes


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

diff --git a/developers-reference.sgml b/developers-reference.sgml
index fbf711d..d8155a7 100644
--- 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.183 $">
+  <!entity cvs-rev "$Revision: 1.184 $">
   <!-- if you are translating this document, please notate the CVS
        revision of the developers reference here -->
   <!--
@@ -3553,18 +3553,20 @@ Lisp packages should register themselves with
           <heading>Architecture-independent data</heading>
           <p>
 It is not uncommon to have a large amount of architecture-independent
-data packaged with a program. For example, collection of icons,
-wallpapers or other graphic files, or audio files. If the size of
-this data is negligible compared to the size of the remainder of the
-package, you can keep it all in the same package.
+data packaged with a program.  For example, audio files, a collection
+of icons, wallpaper patterns, or other graphic files.  If the size of
+this data is negligible compared to the size of the rest of the
+package, it's probably best to keep it all in a single package.
           <p>
 However, if the size of the data is considerable, consider splitting
-it out into a separate, architecture-independent package
-("_all.deb"). By doing this, you avoid needless duplication of the
-same data into eleven or more .debs per each architecture. While
-this adds some extra overhead into the Packages files, it can save a
-lot of disk space on Debian mirrors, and it also reduces processing
-time of Lintian or Linda when run over the entire Debian archive.
+it out into a separate, architecture-independent package.
+("_all.deb").  By doing this, you avoid needless duplication of the
+same data into eleven or more .debs per each architecture.  While this
+adds some extra overhead into the <file>Packages</file> files, it
+saves a lot of disk space on Debian mirrors.  Separating out
+architecture-independent data also reduces processing time of
+<prgn>lintian</prgn> or <prgn>linda</prgn> (see <ref id="tools-lint">)
+when run over the entire Debian archive.
         </sect1>
       </sect>