From: aph Date: Sat, 22 Feb 2003 20:59:51 +0000 (+0000) Subject: bpp-archindepdata: eliminate leading space, no change in content at all X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?a=commitdiff_plain;h=e0c979b14c5e1aa9cb221b068cecdf0daed7d063;p=developers-reference.git bpp-archindepdata: eliminate leading space, no change in content at all git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@2178 313b444b-1b9f-4f58-a734-7bb04f332e8d --- diff --git a/developers-reference.sgml b/developers-reference.sgml index 063538a..fbf711d 100644 --- a/developers-reference.sgml +++ b/developers-reference.sgml @@ -6,7 +6,7 @@ %commondata; - + - Architecture-independent data -

- 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. - -

- 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. - - + + Architecture-independent data +

+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. +

+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. +