Summary: | x11-libs/libxcb-1.7 shouldn't RDEPEND on x11-proto/xcb-proto | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Maxim Kammerer <mk> |
Component: | New packages | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | flameeyes |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=342393 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Maxim Kammerer
2012-01-15 11:15:42 UTC
The problem is probably similar to bug 342393. While libxcb does not strictly runtime-depend on xcb-proto, packages that build against libxcb might fail if xcb-proto is not installed. I have temporarily put xcb-proto in package.provided, unmerged it, and rebuilt the libxcb-dependant packages that I have: [ebuild R ] x11-libs/libX11-1.4.4 USE="-doc -ipv6 -static-libs -test" 0 kB [ebuild R ] x11-libs/xcb-util-0.3.8 USE="-doc -static-libs -test" 0 kB [ebuild R ] x11-drivers/xf86-video-intel-2.17.0-r3 USE="dri sna" 0 kB [ebuild R ] x11-apps/xdpyinfo-1.3.0 USE="xinerama -dga -dmx" 0 kB [ebuild R ] x11-apps/xlsclients-1.1.2 0 kB [ebuild R ] x11-apps/xwininfo-1.1.2 0 kB [ebuild R ] x11-libs/startup-notification-0.12 USE="-static-libs" 0 kB All merged fine. Maybe xcb-proto can be move to DEPEND after all. /usr/lib/pkgconfig/xcb-ewmh.pc:Requires: xcb xcb-proto Not sure if any package in tree builds against that. (In reply to comment #3) > /usr/lib/pkgconfig/xcb-ewmh.pc:Requires: xcb xcb-proto > Not sure if any package in tree builds against that. Doesn't seem so: # find /usr/portage -name '*.ebuild' | xargs grep -l xcb-util-wm /usr/portage/x11-libs/xcb-util/xcb-util-0.3.8.ebuild /usr/portage/x11-libs/xcb-util-wm/xcb-util-wm-0.3.8.ebuild Hi, any news? Can xcb-proto be moved to DEPEND? (In reply to comment #5) > Hi, any news? Can xcb-proto be moved to DEPEND? No. Not really. Portage needs to support a new kind of DEPEND for this case. After looking at the pkgconfig files, it appears mostly safe to drop the RDEPEND on xcb-proto. The only package that needs to be adjusted appears to be xcb-util-wm, which should have the xcb-proto dependency anyway as xcb-ewmh.pc requires xcb-proto. Can I proceed with this as QA? I'm hitting this on one of my projects. (In reply to comment #8) > Can I proceed with this as QA? I'm hitting this on one of my projects. Yes, please. The dependency on xcb-proto was changed to build-time only. Regarding the xcb-util-wm, the pkconfig entry seems bogus at first glance, but that is something upstream will have to address. This change broke cross compiling, bug 412909. |