On Wednesday 05 August 2009 13:04:47 Elmar Stellnberger wrote:
On the other hand why not keep a functionality which is already implemented and might make sense in some cases. My suggestion for this would be to keep dup but to make it always require the --force option.
Why staying with the inferior algorithm (as default)?
This will require no additional implementation effort (unless the check I have previously proposed). If --force is not specified alongside with dup --repo a message should prompt the user either to use --from instead or to add the --force option.
I'd say 'NO', because -- independently form any --force -- the computed transaction might be worse, than the one computed by upgradeRepo. It may very well be that additionally updating a package in an other repo allows to keep a bunch of packages instead of removing them. The solver will also try harder to keep a package which has an update path to some known repo, than an orphaned one (one not provided by any repo). The current 'dup -r' declares too many packages as orphaned. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org