Re: git: b2eed2d66478 - main - wayland: add wayland virtual category

Baptiste Daroussin <bapt@FreeBSD.org> writes:

> On Fri, Jul 01, 2022 at 01:51:32PM +0200, Jan Beich wrote:
>
>> Baptiste Daroussin <bapt@FreeBSD.org> writes:
>> 
>> > The branch main has been updated by bapt:
>> >
>> > URL: https://cgit.FreeBSD.org/ports/commit/?id=b2eed2d66478efa63594275ffecd1be2d565c983
>> >
>> > commit b2eed2d66478efa63594275ffecd1be2d565c983
>> > Author:     Baptiste Daroussin <bapt@FreeBSD.org>
>> > AuthorDate: 2022-07-01 08:00:55 +0000
>> > Commit:     Baptiste Daroussin <bapt@FreeBSD.org>
>> > CommitDate: 2022-07-01 08:01:22 +0000
>> >
>> >     wayland: add wayland virtual category
>> 
>> But why? What does "wayland" here actually means? Otherwise, looks
>> similar to "ipv6" virtual category in the past. Easier to list what
>> doesn't yet or cannot support Wayland.
>> 
>> For example, Porter's Handbook defines "wayland" virtual category as
>> "Ports to support the Wayland display server". This is ambiguous because
>> "server" means Wayland compositors, and Xwayland can bridge X11 clients.
>
> The porter's handbook definition has clearly be written by someone who probably
> knows very little about Wayland.
>
> Making a strong definition of what the wayland virtual category is, is probably
> hard, the point of flagging a port in the wayland category is to make it easy to
> search for an application supporting wayland via: pkg search -g "wayland/*" for
> example.

OK. Adding leaf ports with explicit (e.g., firefox) or designed around
Wayland (e.g., pam_xdg) support kinda helps with discoverability. Complications
are X11-agnostic apps with Wayland support handled entirely by toolkit
(e.g., many gtk3 and all gtk4 apps) and protocol compatibility (wlroots,
weston, kwin, mutter, etc).

Otherwise,

  $ pkg search -g "wayland/*"

almost duplicates

  $ pkg rquery "%rn" wayland | xargs pkg rquery "%o\t%c"