Alan Grimes wrote: > 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. =\ >
I have no use for windoze. I don't use it, never have and don't have any plans to use it either. Sounds like windoze may be more to your liking tho. It updates itself without you having to do anything. I do have friends that use windoze so I have a idea on how it works. Recent changes in emerge/portage did not break anything otherwise there would be dozens of other people on this list having the same type of problems you are having. So, it's not emerge/portage. The problem, as has been said many times before, is your script and your update process. That is your problem. I might also say, yes, you decide how to run your computer. That also means that when you use something such as the script you posted a while back, you can also keep the pieces as well. Even a developer will tell you that. >> 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...) So, what you are saying is that the next time you run your script and thoroughly break things again, you will come back, start a new thread griping and moaning about the problem you brought on yourself? How lovely. Just so you know, a couple people posted that they blacklisted you. They won't see your emails any more. I'm getting close to it myself. I keep hoping it will get through to you that you need to change what YOU are doing instead of doing what you want which breaks things. At some point, there won't be anyone left here reading your messages even if you decide to change how you do things. Basically, it could get worse. > 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... =\ > May I remind you that Gentoo doesn't work that way? Wasn't that you claiming you been using Gentoo for years and you haven't figured that out yet? No wonder you having so much trouble and have that script you do. If I had a install that I wanted to trash, I'd use your script. It would be a dandy start to totally screwing up a install. This is the update process I use, not that you would ever consider using something sane or anything. First command. eix-sync && emerge -uvaDN world That syncs the tree, and overlays if I have any, and then spits out a list of packages that will be updated/installed. You can automate/script that and even have it emailed to you if you want. At that point, I LOOK at the list. If I don't like a USE flag, I go change it. If I don't like a version of something, I go find and edit whatever config file that will give me what I want. If I want to skip something, I add the --exclude <package name> to the update command and see what the list looks like again. If, big IF, it looks OK, I hit "y" and let it start updating. 99 times out of a 100, it updates with no problems at all. The biggest thing, I NEVER, NEVER, do a update without looking at the list and making certain that the list is OK. Once that process is done, I run --depclean, eclean and whatever other housekeeping that needs to be done including updating config files if needed. I think you came here to gripe. Several of us have tried repeatedly to help you and you IGNORE every thing we tell you. We have told you that your script is a disaster. The fact that you continue to have this trouble whenever you do a update should prove that to anyone who can have a thought in their head. You seem to miss that point. Now that you have likely alienated just about everyone on this list, why not post how the problem is about something besides you some more. At some point, you won't get a single reply from someone even trying to help you at all. Here's a thought to ponder. If you keep doing the same thing and expect a different result, what are you? You keep using that script and expect it to work when it won't. Better wise up soon. Dale :-) :-)
