| 1 |
Mark Knecht wrote: |
| 2 |
> <SNIP |
| 3 |
> I'm proceeding along getting a number of packages removed which is |
| 4 |
> good. However here's an example one I'm not sure how to handle or why |
| 5 |
> it's showing up. I've run --depclean -p and see what appears to be an |
| 6 |
> unneeded library called libwmf. However when I try tracing my way back |
| 7 |
> to find what depending on it I eventually get to xine-ui which I use |
| 8 |
> all the time: |
| 9 |
> |
| 10 |
> lightning ~ # equery d libwmf |
| 11 |
> [ Searching for packages depending on libwmf... ] |
| 12 |
> media-gfx/imagemagick-6.3.0.5 |
| 13 |
> lightning ~ # equery d imagemagick |
| 14 |
> [ Searching for packages depending on imagemagick... ] |
| 15 |
> gnome-extra/libgsf-1.14.2 |
| 16 |
> media-libs/xine-lib-1.1.2-r3 |
| 17 |
> media-video/transcode-1.0.2-r3 |
| 18 |
> lightning ~ # equery d xine-lib |
| 19 |
> [ Searching for packages depending on xine-lib... ] |
| 20 |
> media-sound/amarok-1.4.3-r1 |
| 21 |
> media-video/xine-ui-0.99.5_pre20060716 |
| 22 |
> media-video/totem-2.16.4 |
| 23 |
> lightning ~ # |
| 24 |
|
| 25 |
This issue can be related to changes in USE flags. xine-lib depends on |
| 26 |
imagemagick only when "imagemagick" USE flag is set. And imagemagck |
| 27 |
depends on libwmf only when "wmf" USE flag is set. So these packages |
| 28 |
were merged probably when you had these flags set. Later USE flags may |
| 29 |
have changed (new portage profile?) and currently they most likely are |
| 30 |
not set. |
| 31 |
|
| 32 |
Moreover, I have noticed that equery takes conditional dependencies into |
| 33 |
consideration regardless of USE flags state. Thus it shows that |
| 34 |
imagemagick is required by xine-lib even when it actually isn't (because |
| 35 |
you don't have "imagemagick" flag set). |
| 36 |
|
| 37 |
You have run emerge -uDN, so none of your packages (except those listed |
| 38 |
by -p --depclean) should be linked with any of libraries to be removed. |
| 39 |
I think that running --depclean will not break your system or when |
| 40 |
something is broken, it will be remerged by revdep-rebuild without |
| 41 |
pulling in removed packages. |
| 42 |
|
| 43 |
Running revdep-rebuild after removing only some packages pending removal |
| 44 |
isn't a good thing, because remaining ones are likely to be broken. I |
| 45 |
recommend running revdep-rebuild after depclean is completed. |
| 46 |
|
| 47 |
Of course, you should earlier revise your USE flags to check whether |
| 48 |
some features needed by you weren't excluded. I cannot also guarantee |
| 49 |
anything, so if it is a critical machine, you should undertake some |
| 50 |
safety steps like quickpkg'ing packages before removal. |
| 51 |
|
| 52 |
Hope it helps, |
| 53 |
Marek Wróbel |
| 54 |
-- |
| 55 |
gentoo-amd64@g.o mailing list |
Archives