On Tue, 2018-02-20 at 15:50 +0100, Johannes Meixner wrote:
Hello,
On Feb 20 10:17 Stefan Seyfried wrote (excerpt):
Just "requires" and "recommends" without hints are not going to solve this.
I think "Requires" never needs a hint because only mandatory stuff (i.e. stuff without it can not at all work) should be required but "Recommends" need hints.
We either install too little (basically "--no-recommends") or too much. IMO the solver needs a hint, maybe "recommended also for smaller sytems" or "recommended, but only when you really want a seriously fat installation". Of course I have no idea how to implement that.
Only an offhanded idea:
Is it perhaps possible to specify conditions for "Recommends" e.g. in bar.spec something like ----------------------------------------------------------- %if %is_already_installed_or_will_get_now_installed foo Recommends: bar_addon_for_foo %endif -----------------------------------------------------------
This is basiclaly possible when using the reverse, Supplementes. for example gimp-plugin-aa contains: Supplements: packageand(gimp:libaa1) So if libaa1 is (for whatever reason) installed on the system, and also gimp is there, the the extension for gimp, making use of libaa1, is being installed as well (as recommended, and can be uninstalled on demand) (and there would be RPM rich deps, which Tumbleweed can't support just yet without breaking all update paths; hence not acceptable for the time being). Furthermore, if one goes to study how 'Recommends' is meant to be interpreter by the package manager [0], it becomes clear that 'Recommends is to be treated the same way as a Requires, with the exception that it is non-fatal if it can't be satisfied'. The other end to that is 'Suggests', which is not auto-installed, but a hint *can* be given to the user by a PM that additional packages are suggested. Cheers Dominique [0] http://rpm.org/user_doc/dependencies.html