Volker Armin Hemmann wrote: > Am 29.05.2016 um 22:15 schrieb Alan McKinnon: >> On 29/05/2016 19:54, Dale wrote: >>> Alan McKinnon wrote: >>>> On 29/05/2016 11:28, Dale wrote: >>>> Well, he did reply. Either his script is still doing it or he did >>>> and he hasn't learned anything yet. It's funny how he is the only >>>> one that has these problems and how he keeps using that disaster of >>>> a script. I don't think anyone has posted a positive thing about >>>> that script. I'm no script guru by any means but even I can read >>>> that thing and see what a disaster it is. Best of luck to him. I'm >>>> about done trying to help. Key word, trying. Dale :-) :-) >> I agree Dale. >> >> Mr Grimes should probably move over to Linux From Scratch. It has none >> of portage's absurdities, makes no effort at all to be helpful to the >> user and allows anyone to write any build automation they feel is >> appropriate. LFS also requires you to watch all the compiler output all >> the time to catch problems; it all seems to match Mr Grimes' >> requirements right down to a tee. >> >> >> I'm going to STFU down, go to bed and finish an astonishingly intriguing >> Stephen King book and let the computer get on with doing whatever it >> thinks perl-cleaner fixes. >> > personally, I hope he stays around. His mails and the resulting threads > amuse me. > >
On one hand, it is somewhat funny to read. On the other, it is really silly. Jeez, I've had things go sideways before, hal comes to mind, but I don't use a script like he does and bring it on myself. Heck, I can remember when the update process was emerge sync and emerge -uvp world. Look at list, then remove the -p part. Then pray there was no build failure from a bug. Then portage, both the emerge command and the tree and all its ebuilds, started improving. Slots came along and a whole ton of other things. Nowadays, eix-sync && emerge -uvaDN world and generally, it's ready to update. Once that is done, a little housekeeping and it's done. Of all the problems I have, it is usually something I overlook that I did or just a general build failure. Sometimes a retry gets it going again. Thing is, emerge has changed over the years. All of us have adapted to those changes and adapted our own systems and process to what works. Some systems may be fine with a backtrack that is the default. Some may need it set to 30, some 100. Thing is, setting it to 0 to disable it or something, that won't likely work to well. Grimes seems to want to disable some of the new features thinking it will make it easier but it's making it harder. Portage/emerge will do the heavy lifting if you let it. Anyway, I'll give it another go or two and after that, he will have to figure it out on his own. I like helping when I can but sometimes, you just have to let them get hungry enough to fish for themselves. lol Dale :) :-)
