1 |
051130 Chris Gianelloni wrote: |
2 |
> On Wed, 2005-11-30 at 17:34 -0500, Philip Webb wrote: |
3 |
>> As one of the "masses", I am certainly disturbed at that implication. |
4 |
>> I don't remember any such need when I upgraded 2.9.5 -> 3.x (now 3.3.6). |
5 |
>> This is the kind of issue on which I trust the devs to do sensible things, |
6 |
>> but do we really need to rebuild our whole systems from the ground up ? |
7 |
>> Ordinarily, I upgrade packages individually when it seems appropriate |
8 |
>> & never do 'emerge world' with or without '-e' or other flags; |
9 |
>> I do 'esync' every weekend & look at what is marked as having changed. |
10 |
> Technically, you don't need to rebuild world. |
11 |
> You only need to rebuild stuff that uses C++ and links to libstdc++. |
12 |
|
13 |
That's what I wanted to know. |
14 |
>From this & other responses, it looks as if it would be a bad idea |
15 |
eg to upgrade to KDE 3.5 just before adopting GCC 3.4 (smile), |
16 |
but that 'revdep-rebuild' will reveal the (lengthy) list of needed remerges. |
17 |
|
18 |
I would urge whoever is documenting this |
19 |
to avoid a blanket recommendation to 'emerge -e system && emerge -e world' |
20 |
or be prepared for a lot of negative reaction from the masses. |
21 |
|
22 |
<spectate> |
23 |
|
24 |
-- |
25 |
========================,,============================================ |
26 |
SUPPORT ___________//___, Philip Webb : purslow@××××××××××××××.ca |
27 |
ELECTRIC /] [] [] [] [] []| Centre for Urban & Community Studies |
28 |
TRANSIT `-O----------O---' University of Toronto |
29 |
-- |
30 |
gentoo-dev@g.o mailing list |