Summary: | cairo lost its gl pkg-config dep (ddccontrol[gtk] build fails when x11-proto/{glproto,dri2proto} are uninstalled) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | mjan96 |
Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | cardoe, x11 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | complete build.log for failed build |
Description
mjan96
2011-01-29 12:52:25 UTC
Created attachment 260988 [details]
complete build.log for failed build
not a bug in ddccontrol. ddccontrol only needs gtk+/gthread. those packages need other things, but those are the problem of those other packages. in this case, it seems like it's a matter of: ddccontrol needs gtk+ gtk+ needs cairo cairo needs gl gl needs glproto whether this is user error or something else, that's prob for the gnome/cairo guys to decide $ equery depgraph --depth=3 =app-misc/ddccontrol-0.4.2 | grep glproto [ 3] x11-proto/glproto-1.4.14-r1 $ equery depgraph --depth=3 =app-misc/ddccontrol-0.4.2 | grep dri2proto [ 3] x11-proto/dri2proto-2.6 glproto and dri2proto are correctly present as indirect (depth 3) dependencies of ddccontrol; uninstalling them and then trying to install ddccontrol is a user mistake. To ensure that none of the indirect dependencies of a package that you are building are missing, it is recommended that you use "emerge --deep" instead of just "emerge" (see man emerge for more information). Using --deep is especially important if you have been cleaning up your system by manually unmerging packages that you might have thought were unneeded. |