1 |
On Mon, Mar 12, 2012 at 1:53 AM, Helmut Jarausch |
2 |
<jarausch@××××××××××××××××.de> wrote: |
3 |
> Hi, |
4 |
> |
5 |
> even the most recent portage 2.2.0_alpha90 has difficulties handling |
6 |
> @preserved-rebuild especially after many binary emerge operations. |
7 |
> It tries to re-emerge the same packages again and again. |
8 |
> As a last resort I have to remove /var/lib/portage/preserved_libs_registry. |
9 |
> But after that the old libraries are still hanging around and revdep-rebuild |
10 |
> won't since there aren't any broken libs or binaries just some which are |
11 |
> linked against old versions. |
12 |
> Is there an elegant way to find these old libraries? (Removing them would |
13 |
> alert revdep-rebuild afterwards). |
14 |
> |
15 |
> Thanks for a hint, |
16 |
> Helmut. |
17 |
> |
18 |
|
19 |
Hi, |
20 |
I haven't tried Neil's method so I cannot comment on that. |
21 |
|
22 |
Personally I actually start with |
23 |
|
24 |
revdep-rebuild -ip |
25 |
|
26 |
to see if anything is flagged. If there is then I run |
27 |
|
28 |
equery depends whatever-was-found |
29 |
|
30 |
and |
31 |
|
32 |
equery belongs whatever-was-found |
33 |
|
34 |
to see what uses (if anything) and what owns (if anything) |
35 |
whatever-was-found. If nothing uses or owns then I delete it by hand. |
36 |
|
37 |
It's labor intensive. Possibly Neil's metthod gets around some of |
38 |
that. However I've used this for years and seldom had too many things |
39 |
to clean up, and what I have had wasn't too difficult to work though. |
40 |
There were some issue with Flash on one of my machine last week that |
41 |
took awhile to dig through. |
42 |
|
43 |
I try to do my machine once every couple of months. |
44 |
|
45 |
HTH, |
46 |
Mark |