Hi Ludwig,
Ludwig Nussel
Hi,
Some packages split out their man pages or other documentation into a sub package. More often than not that subpackage then is recommended. IOW installed by default which is undesirable. We also have a pattern for documenation though. So IMO it makes sense to link installing such documenation packages to the pattern. The question is how though.
Assuming we have foo, foo-doc and patterns-base-documentation I see several ways:
1. pattern is in charge a. in patterns-base-documentation Recommends: foo-doc b. in patterns-base-documentation Recommends: foo-doc if foo
2. package is in charge a. in foo Recommends: foo-doc if patterns-base-documentation b. in foo-doc Supplements: packageand(foo:patterns-base-documentation)
1) pro: when looking at the pattern eg. in YaST one can actually see an overview of what documentation is available. con: pattern needs to be adjusted for every change in packaging. Extra step and easy to forget.
2) pro: packager can add, split, merge or drop packages any time con: package installation is a bit more black magic. The pattern leads to pulling in more packages than expected.
I would be in favor of 2), because 1) requires an additional step for
every packager and thus will probably be skipped. Also, 2) should be
verifiable via a rpmlint rule, whereas 1) isn't easily doable.
Cheers,
Dan
--
Dan Čermák