[Bug 227509] graphics/mesa-{dri,libs}: enable WAYLAND by default
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Oct 15 20:09:11 BST 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227509
Jan Beich <jbeich at FreeBSD.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|graphics/mesa-libs: make |graphics/mesa-{dri,libs}:
|WAYLAND default on |enable WAYLAND by default
Depends on| |227423
Keywords| |needs-qa
Alias|wayland at mesa-libs |
--- Comment #7 from Jan Beich <jbeich at FreeBSD.org> ---
Bug 227423 will tackle libwayland-egl issue. WAYLAND=on is still required for
other things (Vulkan, libEGL). So, let's change the default to facilitate
testing/maintenance.
https://lists.freebsd.org/pipermail/freebsd-x11/2017-December/020288.html
(In reply to Niclas Zeising from comment #2)
> This needs more thought, since I don't want to add wayland dependencies by default to mesa.
What benefit do you expect from neglecting Wayland support? X11 isn't going
away but in future more Wayland-only apps may appear.
> One idea is to separate out the wayland bits of mesa into a separate port.
> I haven't looked at the details right now though.
Let's not undo bug 218799. Splitting ports adds to maintenance cost and
introduces intradependencies (i.e., dependencies in-between parts, including
loops). Moving into a flavor won't work until the ports framework supports
package alternatives aka variable dependencies, so direct and indirect
consumers don't add up in a conflict between flavored and unflavored
dependency.
> We also have to ensure that we don't break platforms without llvm,
> since wayland requires llvm, at least according to comments in the
> makefile.
Not Wayland but libEGL. Affects only sparc64. Is it that hard to add
OPTIONS_EXCLUDE_sparc64=WAYLAND ?
Referenced Bugs:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227423
[Bug 227423] graphics/wayland: update to 1.16 (libwayland-egl NOW LIVES HERE!)
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kde-freebsd
mailing list