![](https://seccdn.libravatar.org/avatar/3035b38ff33cf86f480bb169b8500b80.jpg?s=120&d=mm&r=g)
https://bugzilla.novell.com/show_bug.cgi?id=389694
User visnov@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c8
Stanislav Visnovsky
(In reply to comment #3 from Stefan Schubert)
comment #1: 2. "zypper (resp. sat-solver) should only honor those recommends/supplements which belong to the current transaction" That would break our new feature installing language depend packages or additional kmp packages if a repo or a new hardware has been installed by the user.
Whooo, may be a cool feature, but also one of the most annoying ones, really. Especially if we don't provide a way to get away with these automatic additional packages!
comment #2: a, see above b, That would be too generally and not understandable for the user while future zypper/UI calls.
Hm. But how to solve this then? zypper in foo wants to install a lot of totaly unrelated recommended packages and there is no way to get away with them other than always using --no-recommends or by letting them to install and them removing them manually one by one.... we _need_ an acceptable solution for this.
IMO, b) would be a good solution. Why do you think it would confuse users? You run zypper in, check what it's going to install, you don't like it, you retry with --no-recomends, you like it. Soft locks saved, you won't see the then would-be-selected recommends automatically popping up again. What's wrong with that?
This is usability nightmare. The first impression counts and here is the impression 'I told zypper to do one thing and it does another one'. It is even unclear that user should use '--no-recommends'. I agree with comment #4. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.