On Saturday, April 16, 2016 07:07:16 PM Dale wrote: > J. Roeleveld wrote: > > On Saturday, April 16, 2016 11:25:23 AM Dale wrote: > >> Top posting since John started it. lol > > > > Refusing to top-post, even when others do... > > Makes for even more fun to trace the conversations... > > > >> Can you two explain this to Alan Grimes? He seems to think emerge has > >> some very serious problems. ;-) > > > > Trying to explain it to him will be as useful as discussing science with > > members of the Westboro Baptist Church or similar.... > > I was thinking fence post but we have the same idea. ;-)
You're referring to a LART? http://www.urbandictionary.com/define.php?term=LART > >> I might add, I recently went through the KDE plasma update which > >> involved a ton of rebuilds/upgrades. Since I run a mix of stable and > >> unstable, it took some effort to get it all sorted BUT emerge did a > >> pretty good job of telling me what was needed. Once I got the proper > >> things in the keyword and USE file, it was off to compile land for > >> several hours. I might add, I had to use some of Alan McKinnion's logic > >> to understand emerge's output. > > > > Aside from that, the upgrade guide was a very useful step-by-step guide to > > avoid any blockers during the upgrade. > > Actually, I think the only info I got from it was that I had to switch > to sddm and emerge the plasma package. Since I have a mix of stable and > unstable here, it went down a whole new path after that. I had hard > blockers, other packages that had to be keyworded and to change some USE > flags as well. If I was running stable only, then the guide would > likely have worked step by step. It did give the basic info that I > needed even tho I was running a install that was different. It also gave some commands on how to find packages you'd need to temporarily remove from the world-file. > The big point tho, emerge did a pretty darn good job of dropping bread > crumbs on what needed changing. On a couple occasions, it took me a few > reads to grasp what it was saying but it was there and I was able to > figure it out. So, unlike Alan G and his problems, emerge did a good job. > > >> I might add, I also recently did a emerge -e world. Out of all the over > >> 1,400 packages installed on this machine, only one failed. I can't > >> recall the package name but I seem to recall keywording to a newer > >> version and that worked. Still, 1 out of over 1400 packages. That's > >> pretty dang good. About 99.9% success. Almost like 24 caret gold. > > > > 1 out of 1400 is, in my opinion, 1 too many. > > But compared to the likely 400 you'd have had about 5 or 6 years ago, I am > > extremely pleased. > > That is what I was talking about. Many years ago, even thinking you > could do a emerge -e world of that many packages without at least a > dozen failures of some kind would be nuts. I'm talking rooms with > rubber walls nuts too. Actually, if I had not forgot to keyword that > new version, it would have worked. That version had already failed and > I should have done the keyword change first. So really, it was my fault. Not removing failing versions.... Like to life dangerously? > >> It seems you two are not alone on being some happy Gentooers. :-D > > > > Count me there as well. > > I have long passed the point where I will accept bad and unreliable > > systems > > when I can help it. > > The longest uptime I have ever had was running Gentoo. If it wasn't for > power failures, I may not ever reboot this thing. lol Same here, but I tend to reboot only for kernel upgrades. Power failures don't happen that much here. -- Joost
