Dale wrote: > Do you really want a answer to that? Seriously? You asked so I guess > you do. Here it is. Yes! lol The way you do things, and continue to > do things, even after having several VERY experienced users tell you > that the way you are doing things is wrong pretty much says it all. If > I post that I was doing something and getting a bad result and someone > such as Neil and/or Alan McKinnon tells me I am doing it wrong, you can > bet your last dollar that I am about to change how I do things. Why, if > either or both of them tell me I am doing something wrong, I'm doing it > wrong. If I continue to do things the same way, well, that would be my > fault not members of this list or emerge/portage. So far, I don't > recall seeing a single post that supports how your script is set up. > Not one, except you of course.
This is linux, not Windows 10. The key difference is that I get to decide how I want my computer to run. =| What I am saying is that recent changes have broken a usage pattern that I was quite content with for more than a decade. =\ > Here's a idea. Since YOU are the only one having this problem, why > don't YOU change what you are doing to something that actually works? > What you are doing doesn't work. Try something else. Funny how those > "stupid" checks work for everyone else. I'm at 193/250 right now so therefore all discussion of changing my procedures is tabled until the next time I have troubles (next month...) >>>> I mentioned this before. If you keep posting but then refuse to accept help, people will start ignoring or blocking your messages. Based on the posts that I see, I suspect some may have already. At some point, even I will. I've only ever blocked one other person on this list. I can see that doubling at some point because you don't come here for help or accept any when it is given. You just come here to gripe about things not working like you want when it is your method that is broken. <<<< May I remind you that most modern software has a "check for updates" button that is fully automated... May I also point out that the stated gentoo update process, of "emerge sync ; emerge --update world rarely actually works or does not have the intended effect without a several dozen qualifiers. I point out here that the qualifiers I use were selected from the ones provided by portage. Now, the question is what qualifiers to use... Regardless of what qualifiers you use you will have errors. So therefore you are forced to do something to recover from those errors. I have found that it never hurts to blindly skip the current package and try the next, so that's exactly what I do. When I saw that my updates always had the same sequence of commands, I wrote the first versions of my scripts. Since then, I have edited, and enhanced my scripts to either take advantage of good new features such as the built-in keep-going command, or to disable features that features, that even once, caused me problems, then I do so. If disabling a feature, even once, solves a problem I will never attempt to use that feature again. So I come here looking for something else to disable because, obviously, the problem is that it is checking something that it would be better off not checking because the problem it seems to think will happen either won't happen or will be so trivial that it won't have any lasting effects on the system. The costs in frustration for the check and trying to satisfy the check being many orders of magnitude greater than whatever emerge was doing before the incident involving water skis, a ramp, and the proverbial SHARK. Instead I'm told that I'm an idiot and should switch to some unspicified but vastly more laborious process involving manually second-guessing the build order or some such nonsense... =\ -- IQ is a measure of how stupid you feel. Powers are not rights.
