| 1 |
Alan Grimes wrote: |
| 2 |
> Peter Humphrey wrote: |
| 3 |
>> Read the manual. |
| 4 |
>> ...and get rid of all those excruciating scripts of yours and start doing |
| 5 |
>> things manually and sanely, one step at a time. |
| 6 |
> |
| 7 |
> Repeat the following three times daily: |
| 8 |
> |
| 9 |
> |
| 10 |
> The purpose of a computer is to save me time and effort. |
| 11 |
> |
| 12 |
> |
| 13 |
|
| 14 |
How's that working out fer ya so far??? |
| 15 |
|
| 16 |
I'm not good at reading scripts but from what I understand from your |
| 17 |
scripts, it's no wonder you are running into all the issues you are. If |
| 18 |
you want a update process that takes very little time and effort on your |
| 19 |
part, Gentoo is not going to fulfil that requirement. I been using |
| 20 |
Gentoo for well over a decade now. I never do blind updates. Let me |
| 21 |
stress that word, NEVER. I sync the tree, which could be scripted or |
| 22 |
done with a cron job, then I see what needs updating and most |
| 23 |
importantly, what will be changing, which could also be scripted or done |
| 24 |
with a cron job. Some even script that part and have the results |
| 25 |
emailed to them. Some use emerge -p but I use emerge -a for that since |
| 26 |
I do it manually. Then comes the part that requires you and your time |
| 27 |
and effort. You have to look at what is going to be updated and what |
| 28 |
changes are going to be made. I pay very close attention to USE flag |
| 29 |
changes. I also watch for packages that may require other packages to |
| 30 |
be rebuilt. IF, big IF there, everything looks OK I proceed with |
| 31 |
updates. If something looks a little off and I need to see what changes |
| 32 |
will change how software works, then I go research those changes BEFORE |
| 33 |
doing the updates, not after. Sometimes those require me to edit USE |
| 34 |
flags, mask packages, unmask/unkeyword packages so that I get the |
| 35 |
updates I want or DON'T get updates that I'm not ready for yet. The |
| 36 |
thing you seem to not understand yet, only YOU can make that decision. |
| 37 |
The emerge command and portage can't do that for you, you have to do |
| 38 |
that last part. |
| 39 |
|
| 40 |
The way your script works from what I understand, you automate the whole |
| 41 |
process and you get the end result. That result is usually not what you |
| 42 |
want or breaks something which leads you to here and us slapping our |
| 43 |
foreheads at what you did to get here. Honestly, if you keep doing |
| 44 |
things the way you are, you are going to spend a LOT more time fixing |
| 45 |
problems because some folks will let you learn the hard way. You will |
| 46 |
post, a dozen or more will know how to fix it but won't post so that you |
| 47 |
learn on your own. One thing about this mailing list, people expect you |
| 48 |
to at least try and do things in a sane way. Blind updates may work |
| 49 |
fine on Ubuntu or something but it does not work on Gentoo. There are |
| 50 |
just way to many options and changes that can break things. |
| 51 |
|
| 52 |
Here's a hint. Script the sync process. Script the emerge -p part and |
| 53 |
either have it emailed to you or spit out on the screen which is all |
| 54 |
fine and doable with known results. At that point, YOU have to step in |
| 55 |
and spend a few minutes looking at what emerge is about to do. If you |
| 56 |
just blindly update, you get things that are broken at some point and |
| 57 |
could be badly broken. It shouldn't be a surprise or a big shock when |
| 58 |
things break. Several others have posted that the way you are doing |
| 59 |
things is how you got those breakages. If you keep doing things the |
| 60 |
same way, expect more breakages. You will likely get less help too. |
| 61 |
|
| 62 |
Just my $0.02 worth. You can take that and make it valuable or throw it |
| 63 |
away and make it worthless. |
| 64 |
|
| 65 |
Dale |
| 66 |
|
| 67 |
:-) :-) |
Archives