| 1 |
Dale schrieb: |
| 2 |
> Michael Higgins wrote: |
| 3 |
> |
| 4 |
>> I attempted to emerge 'twinkle', a soft phone, but whoever made the ebuild neglected to include a dependency on KDE libraries. |
| 5 |
>> |
| 6 |
>> 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. |
| 7 |
>> |
| 8 |
>> 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. |
| 9 |
>> |
| 10 |
>> But it didn't. Something should, however. |
| 11 |
>> |
| 12 |
>> 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? '-) |
| 13 |
>> |
| 14 |
>> Cheers, |
| 15 |
>> |
| 16 |
>> |
| 17 |
>> |
| 18 |
> |
| 19 |
> I would think --depclean would take care of that. I would use the -p |
| 20 |
> option at first and make sure it is not going to remove something you |
| 21 |
> want to keep. |
| 22 |
> |
| 23 |
> Dale |
| 24 |
> |
| 25 |
> :-) :-) |
| 26 |
> |
| 27 |
> |
| 28 |
hi, |
| 29 |
you can also use --depclean -av so you want have to tip twice ;-) |
| 30 |
kh |
Archives