1 |
Alan Grimes wrote: |
2 |
> Michael Jones wrote: |
3 |
>> My reason for replying initially was that I didn't think it was fair |
4 |
>> to make light of users who don't expect to *need* to scrutinize the |
5 |
>> output of emerge every single time they run it. Those people exist |
6 |
>> (hi, nice to meet you), and it's not fair to say they're wrong or |
7 |
>> somehow making a grave error in judgement. |
8 |
>> |
9 |
>> It's entirely fair to say that they are treading on thin ice, and that |
10 |
>> if they choose to do this they should understand the risks, but it's |
11 |
>> not fair to say they're automatically wrong to use the tool in a way |
12 |
>> that the tool allows itself to be used. |
13 |
>> |
14 |
>> Either way, we don't need to turn this into a long and in depth |
15 |
>> discussion, so I probably won't reply to the list again unless you |
16 |
>> have any specific questions or concerns for me. |
17 |
> Thank you for the reasonable response. |
18 |
> |
19 |
> Dale, of course, has spewed hate at me for simply trying to make my life |
20 |
> as convenient as possible while still using Gentoo over here without |
21 |
> even providing a satisfactory answer as to why. |
22 |
> |
23 |
|
24 |
Spewed hate? Make your life convenient? I went back and looked at |
25 |
threads you posted several years ago, before your posting privileges |
26 |
were stopped, not sure what action was taken just that you didn't post |
27 |
for a while. Back then, Neil, the other Alan, myself and several others |
28 |
were trying to help you. Mostly, it was pointed out that the script you |
29 |
were using was causing problems and was certainly not making things |
30 |
easier much less convenient. That's not spewing hate. That's trying to |
31 |
help you with the problem. I might add, I was one of very few who kept |
32 |
trying to help when others had already stopped replying to you. Maybe |
33 |
you forgot that?? |
34 |
|
35 |
If you want a easy way to update your system, I'll list what I do here |
36 |
and it has worked for a long time. I been using Gentoo since early |
37 |
2003. Sure, sometimes I run into a issue that I need help on but that |
38 |
isn't to often. When it does, I post all the info I think is needed for |
39 |
others to look at and advise on how to proceed. Sometimes, it is a |
40 |
change upstream, sometimes it is something I have going on on my end. |
41 |
Either way, I adjust to the fix. |
42 |
|
43 |
First, sync the tree and any related overlays. I use eix-sync since it |
44 |
does all of it in one command. It syncs the tree and any overlays at |
45 |
the same time. My first command looks like this. |
46 |
|
47 |
eix-sync && emerge -uvaDN world |
48 |
|
49 |
Since I have some default options in make.conf, it ends up like this for |
50 |
emerge. |
51 |
|
52 |
emerge --jobs=5 --update --backtrack=100 --keep-going --verbose --newuse |
53 |
--oneshot --quiet-build=n --with-bdeps=y --unordered-display --ask |
54 |
--deep world |
55 |
|
56 |
That looks long but most of that is in make.conf so that I don't have to |
57 |
type it all in every time. I also see I can leave off the -u since it |
58 |
is in make.conf. Once the sync is done, it then runs emerge to see what |
59 |
packages are going to be updated, what their USE flags are and if emerge |
60 |
will have any issues emerging them such as hard blocks or USE flag |
61 |
conflicts. I always check for what is being installed new, what USE |
62 |
flags are changing and for upgrades to packages I specifically installed |
63 |
myself. Most changes in the list are color coded. It makes it very |
64 |
easy to see what is changing. If I see something changing that I don't |
65 |
want or want handled another way, I go edit the needed config file(s) |
66 |
and run emerge again to see if it is like I want. Sometimes, that takes |
67 |
a few times. Sometimes, it works fine the very first time. Once it is |
68 |
like I want/need, I then hit y and let emerge proceed with the update. |
69 |
At this point, you can walk away. I run some packages unstable and |
70 |
still it is rare that a package fails. I might add, going over that |
71 |
list usually takes less than five minutes, even if I have to edit a |
72 |
config file to get things like I want. |
73 |
|
74 |
Odds are, if you do it that way, it will work almost every time. The |
75 |
thing is, you have to stay on top of it and update on a regular basis. |
76 |
I saw that was mentioned a few times several years ago. Gentoo supports |
77 |
going a year without a update but it doesn't mean that updating a system |
78 |
10, 12 or 13 months out of date is going to be easy. Depending on what |
79 |
changes has been made, it could be difficult. |
80 |
|
81 |
Maybe when you get the current issue sorted out, you will at least |
82 |
consider this a starting point for doing what is known to work well. It |
83 |
took me years to get to this point. As options are added to emerge, I |
84 |
adjust make.conf to make things work better. Thing is, I don't mind |
85 |
sharing a good way to update and save someone else a lot of issues. |
86 |
It's up to them whether they want to use it or not. |
87 |
|
88 |
I hope this will help you after you get the current problem fixed. |
89 |
|
90 |
Dale |
91 |
|
92 |
:-) :-) |