1 |
On Thursday 07 September 2006 23:34, michael@×××××××××××××.com |
2 |
wrote: |
3 |
> I'm upgrading my gcc from 3.x to 4.x. I've done the gcc |
4 |
> switching, and now I'm updating my system. |
5 |
> |
6 |
> The recommended steps are: |
7 |
> |
8 |
> # emerge -eav system |
9 |
> # emerge -eav world |
10 |
> |
11 |
> While emerging my system I received a message suggesting I |
12 |
> run revdep-rebuild: |
13 |
> |
14 |
> warning - be sure to run revdep-rebuild now |
15 |
> |
16 |
> My question is, should I run revdep-rebuild right after |
17 |
> emerging the system, or should I wait until after I emerge |
18 |
> world? My concern was that in between, my system is in an |
19 |
> unstable intermediate state, and it might be damaged by a |
20 |
> revdep-rebuild in between. |
21 |
|
22 |
There's no need to run revdep-rebuild, whatever you do it will |
23 |
be redundant. The notices you are seeing are primarily intended |
24 |
for when you explicitly emerge packages that other packages may |
25 |
link to. So everything that might be relevant to the notice you |
26 |
see is going to be recompiled anyway when you run 'emerge -e |
27 |
world'. |
28 |
|
29 |
As previously noted on this list, the mention of using |
30 |
revdep-rebuild as a shortcut when upgrading gcc was intended |
31 |
for the move from 3.3 to 3.4 *only*. The specifics of that |
32 |
upgrade made this shortcut possible, in all other upgrades you |
33 |
definitely don't use it. i.e. the guide is in need of an uodate |
34 |
to make this explicitly clear. If you need more info, ask |
35 |
Richard for the inside dope - he's the resident gcc expert |
36 |
around here :-) |
37 |
|
38 |
alan |
39 |
-- |
40 |
gentoo-user@g.o mailing list |