http://bugzilla.novell.com/show_bug.cgi?id=549940
http://bugzilla.novell.com/show_bug.cgi?id=549940#c6
Michael Andres changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |ma@novell.com
Resolution|FIXED |
--- Comment #6 from Michael Andres 2009-11-27 14:14:07 UTC ---
Hmm...
# zypper in -t package test
# grep force_resolution zypper.log
2009-11-27 14:52:15 <1> Fibonacci(26426) [zypper++]
solve-commit.cc(set_force_resolution):271 force resolution: true
^^^^
but
# zypper in -t package -t pattern test
# grep force_resolution zypper.log
2009-11-27 14:53:09 <1> Fibonacci(26530) [zypper++]
solve-commit.cc(set_force_resolution):271 force resolution: false
^^^^^
Do you really think it is a good idea to let force_resolution depend on the
ammount and sequence of -t arguments? IMO worse than 'always on' is 'perhaps
on'.
Please consider using force resolve only when deleting, and never when
installing. Then you can make up your mind whether to use --force always or
never, instead of sometimes.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.