... without fixing anything else other than ebuild QA issues, as we
want to allow the EAPI 6 banning to go ahead in a few days.
Signed-off-by: Sam James <sam@gentoo.org>
There have been some updates to the binary builds for Qt stuff that
basically amount to building PyQt6 with USE=speech. It's not yet active
in live codepaths, so patching it out of the testsuite for now. Will
keep an eye on it in the future with attention paid to the
practicalities of USE=speech. Recheck in future version bumps...
Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
Actually, it doesn't use gtk's gdk-wayland backend at all, not even
optionally, so the dependencies are effectively runtime-only. On the
other hand, it does use the X11 one! Make sure that it correctly
requires gtk+[X] when built for X11 -- which is always, as it currently
doesn't support the wayland backend in that bit of code at all. Hence
wayland support being masked at the moment. So we simply don't worry
about that at all for now. :)
Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
Currently, one is forced to compile c-s-d and gtk with the same value of
USE=wayland which makes it difficult to provide generically reusable
binaries. It is better than automagically depending on wayland and then
lacking it, but not ideal. Preferable would be for c-s-d[wayland] to
require gtk+[wayland] but when built without wayland support, to not
care whether gtk itself is.
We now support a mechanism for packages to opt out of gtk providing the
API, for use by packages that don't provide a `-D wayland=true` but
autodetect whether gtk was built with it. Use that mechanism.
Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
The only plugin that uses gtk's wayland support -- or any wayland
support at all -- is the wacom plugin. It is otherwise meaningless to
depend on gtk's wayland support, so rejuggle the dependencies to reflect
that.
Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
Currently, one is forced to compile c-c-c and gtk with the same value of
USE=wayland which makes it difficult to provide generically reusable
binaries. It is better than automagically depending on wayland and then
lacking it, but not ideal. Preferable would be for c-c-c[wayland] to
require gtk+[wayland] but when built without wayland support, to not
care whether gtk itself is.
We now support a mechanism for packages to opt out of gtk providing the
API, for use by packages that don't provide a `-D wayland=true` but
autodetect whether gtk was built with it. Use that mechanism.
Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
Currently, one is forced to compile nemo and gtk with the same value of
USE=wayland which makes it difficult to provide generically reusable
binaries. It is better than automagically depending on wayland and then
lacking it, but not ideal. Preferable would be for nemo[wayland] to
require gtk+[wayland] but when built without wayland support, to not
care whether gtk itself is.
We now support a mechanism for packages to opt out of gtk providing the
API, for use by packages that don't provide a `-D wayland=true` but
autodetect whether gtk was built with it. Use that mechanism.
Signed-off-by: Eli Schwartz <eschwartz@gentoo.org>
Albeit not lifting the mask yet, been going back&forth with
this too much and it is likely that there is other issues
(plus official nvidia-drivers still ships with 1.1.13.1).
Feel free to unmask if want to try.
Closes: https://bugs.gentoo.org/937773
Signed-off-by: Ionen Wolkens <ionen@gentoo.org>
Joonas Niilola
Volkmar W. Pogatzki
Robert Siebeck
Hans de Graaff
Xin Yang
Ulrich Müller
Sam James
Eli Schwartz
Arthur Zamarin
Matthew S. Turnbull
Ionen Wolkens
Michał Górny