Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 627714 - Discrepancy in USE=wayland use
Summary: Discrepancy in USE=wayland use
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo X packagers
Depends on:
Reported: 2017-08-12 18:49 UTC by Michał Górny
Modified: 2019-11-21 22:20 UTC (History)
4 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2017-08-12 18:49:53 UTC
Basically AFAICS there are packages where 'wayland' means 'enable wayland support' and there are packages where 'wayland' means 'support only wayland, and fail hard on X11'. I've also noticed similar problems with gles flags in the past.

I think it'd be nice to have some brainstorm on how to improve this. Maybe we should have separate flags or some other way to clearly indicate which one it is at least.
Comment 1 Mart Raudsepp gentoo-dev 2017-08-13 05:03:11 UTC
I would say those using USE=wayland to mean "use wayland and not work with X11 at all" are wrong here, when there is no USE=X alongside to support X11 too. But I'm not sure how to handle the packages that fail to support both (unless they are wayland compositors or the like). Do we have an initial list of packages where USE=wayland makes it not work on X11 to have a better idea?
Comment 2 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2017-08-13 07:14:25 UTC
media-libs/glfw is the one I've noticed it. Any game using it fails to start when built with USE=wayland. I suppose a good trick to find them would be look for RDEPENDs with '!wayland?'. This yields:

  wayland? ( dev-libs/libinput )
  !wayland? (
    input_devices_wacom? ( >=x11-drivers/xf86-input-wacom-0.33.0 ) )

  !wayland? (
  wayland? (
Comment 3 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2017-08-13 07:15:18 UTC
And yeah, I suppose having explicit REQUIRED_USE="^^ ( wayland X )" would be a better way to clearly indicate 'you can't have both, sorry'.
Comment 4 Mart Raudsepp gentoo-dev 2017-08-13 08:45:51 UTC
gnome-control-center is sort of fine here - it will work with either, just with X it also pulls in the needed X11 input drivers (one of which in turn pulls in libinput too anyways). I suppose we should really do the !wayland part with a X? instead, however..

I'm not sure about REQUIRED_USE so much, ideally glfw could work with either in the same build. Maybe its maintainers have an idea why it doesn't, or maybe it does and the packaging just is as such.

In this conversation please keep in mind that we are likely to enable USE=wayland alongside USE=X by default in GNOME profiles, likely before the year is over.
Comment 5 Mart Raudsepp gentoo-dev 2017-08-13 08:47:17 UTC
Adding glfw and gnome-control-center maintainers to CC for their input
Comment 6 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2017-08-13 09:31:20 UTC
GLES issue split into bug #627758.
Comment 7 Ulenrich 2017-08-13 12:54:08 UTC
Perhaps something like the python_{target,single}:
I did understand that python semantics at once.
Comment 8 Michał Górny archtester Gentoo Infrastructure gentoo-dev Security 2017-08-13 17:28:05 UTC
PYTHON_SINGLE_TARGET is a cheap hack that was needed because we couldn't get a single defaults for all packages. It will eventually be removed when we can rely on GLEP 73 in all packages.