I got case, where some app requires gtk+[wayland] just to compile (of course, it might get option to disable wayland someday). But anyway, i now have to enable wayland for gtk+:3. But on attempt to rebuild with new use i get conflict: Calculating dependencies... done! [ebuild N ] dev-libs/wayland-protocols-1.11::gentoo 116 KiB [ebuild R ] media-libs/mesa-17.2.8::gentoo USE="classic dri3 egl gallium gbm gles2 llvm nptl pic vaapi vulkan wayland* xa xvmc -bindist -d3d9 -debug -gles1 -opencl -openmax -osmesa -pax_kernel (-selinux) -unwind -valgrind -vdpau" ABI_X86="(64) -32 (-x32)" VIDEO_CARDS="i965 (-freedreno) -i915 (-imx) -intel -nouveau -r100 -r200 -r300 -r600 -radeon -radeonsi (-vc4) -virgl (-vivante) -vmware" 0 KiB [ebuild R ~] x11-libs/gtk+-3.22.19:3::elementary USE="X cups introspection ubuntu wayland* xinerama (-aqua) -broadway -cloudprint -colord -examples {-test} -vim-syntax" ABI_X86="(64) -32 (-x32)" 0 KiB Total: 3 packages (1 new, 2 reinstalls), Size of downloads: 116 KiB !!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: x11-libs/gtk+:3 (x11-libs/gtk+-3.22.19:3/3::elementary, ebuild scheduled for merge) pulled in by x11-libs/gtk+:3 (Argument) (x11-libs/gtk+-3.22.19:3/3::elementary, installed) pulled in by >=x11-libs/gtk+-3.21.0:3[X=,introspection?,wayland=] required by (media-libs/clutter-gtk-1.8.4:1.0/1.0::gentoo, installed) Would not it better depend on 'wayland?' instead if 'wayland=' ?
I'm not sure of the fineprint there offhand. Things need to match up between clutter, clutter-gtk and clutter-gst or something; not sure if that's needed for gtk+. Gilles?
Yep, i self doubt in this... just thought, that if something may be built without, then why not... Is not reason for existing deps is that gtk, built with both x/wayland, might be launched in wayland session, and if it also need clutter/gst, it is going to be in trouble. If so, i'm unlikely insisting on fixing this bug :)
I'm not sure if this is the right place to report, but I ran into a conflict converning media-libs/clutter-gtk with or without wayland. A recent change forced me to enable the wayland flag on a bunch of packages, but clutter-gtk wants -wayland via a dependency by app-pda/gtkpod. Should I file a bug on gtkpod or is my comment here in the right place?
gtkpod doesn't require wayland USE flag to be one way or another. Just the flag needs to match on a bunch of related packages. gtkpod however should see about achieving whatever that one plugin using clutter-gtk does some other way though, as separate clutter packages are pretty much dead and unmaintained upstream.
