Tim Lauridsen wrote:
The next step after the code is included is to add a command line option
to enable it in yum-cli.
should we stick with ''--skip-broken" or is there any better ideas.
IMHO this is the way to go right now. In the long run I think we should
extend the skip-broken code to be also able to handle dist upgrades. This
will require not only ignoring updates but to also remove no longer
supported packages. That way we could also remove the hacks in anaconda to
handle these cases. We implemented this with just a few lines of code in
pyrpm and it works very well. I guess we just have to implement the
"continue" in _skipPackagesWithProblems()
For yum it would make sense to split that up into two options: One that it
guaranteed not to remove a package (skip-broken) and one that pushes the
updates in as far as possible and removes no longer working packages (e.g.
that need an older version of an updated library). We used the term
auto-erase(r) but may be fix-broken is a better term.
Florian
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
