| 1 |
On Thu, 2009-04-02 at 10:49 -0700, 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 |
You should *never* use --prune. It's only there for people looking for |
| 15 |
interesting ways to break their systems. The fact that it didn't remove |
| 16 |
anything indicates that maybe you don't have multiple slots of a package |
| 17 |
installed and you just got "lucky". |
| 18 |
|
| 19 |
Either manually remove the packages using --unmerge or use --depclean |
Archives