Hi b.n., on Mon, Sep 15, 2008 at 10:26:56PM +0200, you wrote: > Seriously: can someone more skilled than me explain why using > --resume-skipfirst and then trying to solve the unmerged packages is/can be > a bad idea? How can this break the system?
Frankly I have no idea. I've heard that argument many times in the
Paludis discussions but never even an attempt at an explanation that
went beyond "it breaks your system". My understanding is that you can
have two kinds of situation if an upgrade fails:
a) the failed package is not a dependency of any other package
b) the failed package is a dependency of at least one other package
In case a) you get to keep the old version, no problem. In case b) the
package that depends on the failed one can
b1) work with the old version
b2) require the upgrade (and say so in the ebuild)
In case b1) things will continue working just fine. In case b2) you'll
get another failed emerge as portage will notice the unmet dependency,
so you get to keep the old version, no problem.
Did I miss anything? Sorry, no flowers today.
cheers,
Matthias
--
I prefer encrypted and signed messages. KeyID: FAC37665
Fingerprint: 8C16 3F0A A6FC DF0D 19B0 8DEF 48D9 1700 FAC3 7665
pgp6nMHlYcdp9.pgp
Description: PGP signature
