1 |
Michael Higgins wrote: |
2 |
> I attempted to emerge 'twinkle', a soft phone, but whoever made the ebuild neglected to include a dependency on KDE libraries. |
3 |
> |
4 |
> Of course, since I don't have KDE libs, emerge failed. But before failing, the ebuild had pulled in, built, and installed two *new* packages. |
5 |
> |
6 |
> As these packages were new dependencies only needed by 'twinkle' (which failed to install), I'd expect running emerge --prune immediately afterward to remove these unnecessary packages. |
7 |
> |
8 |
> But it didn't. Something should, however. |
9 |
> |
10 |
> Rather than my asserting that --prune is broken, since it apparently does *something* (just not what I'd expect), can someone give me a helpful clue as to what WILL remove these unneeded libraries? '-) |
11 |
> |
12 |
> Cheers, |
13 |
> |
14 |
> |
15 |
|
16 |
I would think --depclean would take care of that. I would use the -p |
17 |
option at first and make sure it is not going to remove something you |
18 |
want to keep. |
19 |
|
20 |
Dale |
21 |
|
22 |
:-) :-) |