seth vidal wrote:
On Tue, 2007-12-11 at 14:45 +0100, Florian Festi wrote:
Sorry. It looks like the skip broken code works exactly the opposite way I
thought: It removes the packages that leads to the problem.
I've commited two test cases that give an idea why this might not be the
best strategy (hmm, may be I should add some doc strings...).
There's a lot of the test case you're describing in
testAlternativePackageAvailable() that has much more to do with intent.
if I type
yum install foo bar-1.1
and skipbroken realizes bar-1.1 can't be installed and backtracks it out
and replaces it with bar-ng. I, as the user, am going to be fairly
pissed.
While I agree your opinion from a user perspective I don't think this can
happen with the proposed algorithm. bar-ng can only pulled in while there is
a package requiring it. What can happen is:
yum install foo bar
results in installing foo and bar-ng as bar-ng is needed for foo and bar
cannot be installed. But sorry, that's the best you can get in this situation.
Florian
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
