1 |
Neil Bothwick wrote: |
2 |
|
3 |
>On Fri, 2 Jun 2006 01:46:09 +0200, Hemmann, Volker Armin wrote: |
4 |
> |
5 |
> |
6 |
> |
7 |
>>--deep is dangerous! |
8 |
>> |
9 |
>>I have stopped using --deep ages ago. |
10 |
>>As an example: |
11 |
>> |
12 |
>>there is an --deep update for libFOO.1 to libFOO.1.1. |
13 |
>> |
14 |
>>You make this update which only shows up with --deep |
15 |
>> |
16 |
>>Suddenly all apps, linking to libFOO.1 are dead or crashy or acting |
17 |
>>weired. |
18 |
>> |
19 |
>> |
20 |
> |
21 |
>Dropping --deep won't stop that happening, only delay it. sooner or |
22 |
>later, one of your packages will need libFOO.1.1 and it will be |
23 |
>installed. --deep doesn't cause this problem, it only affects the timing. |
24 |
> |
25 |
> |
26 |
|
27 |
Yep. |
28 |
|
29 |
> |
30 |
> |
31 |
>>That happened to me several times. I see NO reason to use deep. Ever. |
32 |
>> |
33 |
>> |
34 |
> |
35 |
>How about this instance? The OP wants all packages affected by the |
36 |
>profile change to be updated. Without --deep, that won't happen. |
37 |
> |
38 |
> |
39 |
|
40 |
Yep here too. |
41 |
|
42 |
> |
43 |
> |
44 |
>>Reduced the occurences where I have to use revdep-rebuilt to almost nil |
45 |
>>(except that expat tragedy some weeks ago. Man that sucked ;) ). |
46 |
>> |
47 |
>> |
48 |
> |
49 |
>I do a deep update every day, on various architectures. I run |
50 |
>revdep-rebuild -p occasionally, just to make sure everything is |
51 |
>consistent, it rarely picks up anything. |
52 |
> |
53 |
> |
54 |
|
55 |
I do the same thing. That is one reason it is there, to fix things like |
56 |
this. |
57 |
|
58 |
>--deep is an option, and I understand why you choose not to use it, but |
59 |
>on this occasion it is necessary to accomplish the OP's goal. |
60 |
> |
61 |
> |
62 |
> |
63 |
|
64 |
Yep. Sometimes you have to do it just because you got to. |
65 |
|
66 |
Dale |
67 |
:-) :-) :-) |
68 |
-- |
69 |
gentoo-user@g.o mailing list |