On 01/29/2017 03:33 PM, Alan McKinnon wrote: > On 30/01/2017 00:25, Frank Steinmetzger wrote: >> On Sun, Jan 29, 2017 at 03:32:22PM -0600, Dale wrote: >> >>>>> I haven't updated my system for over a year (1year and 3-months). >>>>> I was trying to upgrade my firefox-bin and I'm already running into >>>>> problems. >>>>> >>>>> What is my best option, re-install from scratch, upgrade in stages etc. >>>>> With firefox-bin I'm getting: >>>> >>>> 1 year 3 months isn't usually that bad and it can be done - I've done it >>>> many times myself. However there are gotchas: >>>> […] >>>> - go slowly and deal with one block at a time. A regular emerge world >>>> probably won't succeed so you gotta bite of small chunks >>>> >>>> With those basics out the way, it's a great learning experience. I >>>> recommend you do it at least once. >>> >>> Might I also add, the -t option can reveal what is causing what >>> sometimes. >> >> Add --unordered-display to that (I put it into my emerge default options). >> It will shrink the output by removing duplicate [nomerge] lines and give you >> an easier to understand overview. >> >> A short while ago I updated an old netbook that hadn't seen any action in >> probably 2 years. It took a while (I cloned the HDD and compiled on my main >> rig), but I prevailed, inlcuding KDE 4 upgrades. >> >>> Also, I'd start with @system first, then work on @world. >> >> I use custom sets (basic tools, system utilities, X stuff, media players >> etc) and dealt with one of them at a time, starting with the less intricate >> ones. >> >>> Only bad thing is, KDE, if you have it installed, is in @system because >>> of dependencies, last I checked anyway. >> >> Uhm, KDE will not become part of @system, but you probably can't update kde >> without @system first. Much fun comes from the package renaming from >> kde-base to kde-apps, and now KDE4 isn't even in the tree anymore. (The OP >> hasn't stated whether he actually uses KDE, though.) > > > KDE isn't IN @system, but gets pulled in if you use --update --deep > > However, there's a way out. @system is a defined set of packages (about > 50 or so), not a list of stuff plus all it's deps. So do this: > > emerge @system > > That should keep everything except the list of system packages out of > the dep graph
Thank you Alan for suggestion. Indeed "emerge @system" it limits number of packages to be upgraded. -- Thelma
