Changes between Version 47 and Version 48 of RpmHowToPackagers

Timestamp:

Feb 3, 2017, 11:09:24 AM (8 years ago)

Author:

dmik

Comment:

--

RpmHowToPackagers

@@ -357 +357 @@
 Please note that `PACKAGE-devel-doc` requires `PACKAGE-devel` but make sure that `PACKAGE-devel` does NOT require `PACKAGE-devel-doc` as otherwise this separation will be useless because the documentation sub-package will be implicitly installed each time the development sub-package is installed.
 
+Another benefit of this separation is that (due to `BuildArch: noarch`) the RPM repositories will only have one copy of documentation files instead of multiple copies stored in multiple platform-dependent `devel` packages.
+
 Of course, if you create a new .spec file from scratch, you should separate `devel` and `devel-doc` right away.
 
-Note that in some rare cases user-level documentation may also be quite bulky (especially when it contains a lot of HTML files with pictures, big PDF files, etc). In such cases it may make sense to put it to a separate package, named `PACKAGE-doc` (`%package doc` in terms of the .spec file) similarly to the template shown above. A rule of thumb is that brief documentation (MAN, INFO) should be always installed with the main package and extended documentation, if it's several dozen MB or more, should go to a `doc` sub-package.
+Note that in some cases user-level documentation may also be quite bulky (especially when it contains a lot of HTML files with pictures, big PDF files, etc). In such cases it may make sense to put it to a separate package, named `PACKAGE-doc` (`%package doc` in terms of the .spec file) similarly to the template shown above. A rule of thumb is that brief documentation (MAN, INFO) should be always installed with the main package and extended documentation, if it's several dozen MB or more, should go to a `doc` sub-package.
 
 == Generating debug packages ==