Stephan Kulow schrieb:
On 2/20/20 10:31 AM, Ludwig Nussel wrote:
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.
Thoughts?
There is no way to have option 1 without complete disaster, so having the packager in control through option 2 is preferred, but to the user option 1 is preferred. So how about Yet Another Bot harvesting the packages supplementing patterns-base-documentation to recommend back from the pattern - creating a SR every week?
Could be done with some effort but the benefit would be that the method could also work for the 32bit packages where the approach is currently rather brute force. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer HRB 36809 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org