Context Navigation

Changes between Version 61 and Version 62 of RpmHowToPackagers

-              v61
+              v62
 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.
+== Filtering out unneeded automatic dependencies
+Recent RPM versions support filtering automatic `Provides` and `Requires` dependencies generated by dependency detection scripts. Filtering out some directories from detection or some dependencies from attaching them to the generated RPMs may be necessary in cases where detection scripts give wrong results or when we lack some packages (usually Perl ones) that don't actually break program behaviour.
+The standard dependency generation and filtering facility is described in detail in the official RPM documentation: http://rpm.org/user_doc/dependency_generators.html.
 == Generating debug info packages ==