<!entity % commondata SYSTEM "common.ent" > %commondata;
<!-- CVS revision of this document -->
- <!entity cvs-rev "$Revision: 1.185 $">
+ <!entity cvs-rev "$Revision: 1.186 $">
<!-- if you are translating this document, please notate the CVS
revision of the developers reference here -->
<!--
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
+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, one 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