Duncan <1i5t5.dun...@cox.net> writes: > It's not going to be of much help at the moment, but FWIW, upgrades do > tend to go much smoother if you don't stay away from them so long. > Personally, I try to do them twice a week so there's never too huge a > list, and even when a kde upgrade comes out, while it might be a bunch of > packages, it's almost all /just/ kde, not gcc and baselayout and portage > and a whole bunch of other stuff all at once! However, that's admittedly > a bit obsessive/compulsive.
I like weekly ... it's easier to integrate into my schedule (where most recurring tasks are weekly) as a Thursday morning task. I like later in the week, as well, so that if things do go pear-shaped, I have the weekend to recover, minimizing work disruption. Also, I'd advise against running `emerge --depclean` blind. Either run it with '-pv' and review the output, or run with '--ask' ... though the former is suited better to my "background batch" mode of doing upgrades while working. I can't quantify or even really qualify it, but I've seen --depclean outright lie. :( (udept had a more thorough --spring-clean, but I haven't found a good replacement, yet) > I do hope gcc-config does it for you. Otherwise, I'm getting a bit > worried, as if man is broken, it's reaching pretty far into your system. > Please post updates as you have them, because I /am/ a bit worried, now. Another option might be to get the removed version (gcc-4.3, I believe) re-installed by hell or high-water, re-establishing the missing/broken bits. Hopefully it'll build clean with 4.4, or maybe you can find a quickpkg/binpackage from someone with a sufficiently-similar config. I recently removed an older gcc that --depclean reported unneeded, and had breakage ... I noticed it almost immediately, and was able to get back to a working system with a minimum of fuss. -- ...jsled http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo $...@${b}
pgpaDYDu7iEp7.pgp
Description: PGP signature
