On 24/09/2018 23:13, Thorsten Kukuk wrote:
On Mon, Sep 24, Richard Brown wrote:
I do not think it is "sane" to advocate for the use of --no-recommends in a great many cases.
As long as packager recommends everything they like, even if nobody out there ever heard from it and will not use it even if installed, people will continue to use --no-recommends.
In the old times we had the problem with too many Requires. Now we have the same problem, but only with too many Recommends.
Recommends should only be used, if this adds functionality >> 80% of the users are really using it. And not like > 99,9% will never use it.
I asked last week during a talk our Labs people, if one from them did ever heard of a functionality, which got installed in every Minimalsystem due to a recommends since > 5 years. Nobody ever heard of this. But due to the result (dependencys) of this, a lot of them install with --no-recommends ...
Thorsten
I somewhere have a bug / todo item to go through and remove all the Recommends from the minimal system, given that there is no way to install it with --no-recommends, therefore everything there is either required or not, when my current submission to patterns-base is accepted that will bring tumbleweed back in line with Leap / SLE, and after that there will be another round to tidy a few more things up. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B