Summary: | >=sys-app/portage-2.2_rc22 --depclean wants to unmerge qt even if it's a dependency of other packages | ||
---|---|---|---|
Product: | Portage Development | Reporter: | marcin-zbik |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | nfortino |
Priority: | High | ||
Version: | 2.2 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | My world file |
Description
marcin-zbik
2009-03-26 21:33:35 UTC
Created attachment 186362 [details]
My world file
This is exactly what is supposed to happen. The qt package split into smaller component packages in the last release, and the qt:4 package is now no longer a real package (go look at it). equery doesn't do what you think it does, it just does a simple grep. Here are the lines you are interested in: qca-2.0.0-r2.ebuild: || ( x11-libs/qt-core:4 >=x11-libs/qt-4.2.0:4 ) cmake-2.6.2-r1.ebuild: qt4? ( || ( ( x11-libs/qt-core:4 x11-libs/qt-gui:4 ) >=x11-libs/qt-4.3:4 ) ) As you can see with qt-core and qt-gui, you are covered. For more a accurate reverse dependency check than equery, use emerge -pv --depclean <atom>. So you say what i should believe to depclean? Im still not shure that those packages are unnecessary. For example I have kadu-0.6.5.* which depends on qt-4 I believe, same as qnapi. I know that qt is now metapackage but I thought that all of those packages are required, not just few of them, especially qt-4.* package. Yes, --depclean is very reliable. If you'd like to see reverse dependencies for all installed packages, do emerge -pv --depclean. You can query the dependency strings of an ebuild like this: portageq metadata / ebuild net-im/kadu-0.6.5.1 DEPEND RDEPEND PDEPEND You'll see that it depends on the split ebuilds like everything else does for qt-4. |