On Tue, 16 Sep 2008 18:50:35 +0200, Matthias Bethke 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?
I think you missed an important part of the Gentoo philosophy, that it gives you the loaded gun but it's up to you to not point it at your foot. Not providing options that could potentially break a system in certain circumstances is for a Nanny Distro. Here the ethos is "here's the tool, read the man page and don't blame us if you do something stupid". Does paludis also refuse to unmerge packages in the system set? -- Neil Bothwick Eagles may soar, but Wombles don't get sucked into jet engines
signature.asc
Description: PGP signature
