Upstreams remmina-1.4.13 introduced wayland as a mandatory component, but only forces wayland in configure.
Recent ebuild followed these changes. Related bug:
Created attachment 698160 [details]
Proposed remmina ebuild makes wayland optional introducing it as a use flag.
Created attachment 698163 [details, diff]
Proposed patch used by the ebuild.
I see this patch was applied upstream, but... is it an automagic dep now or is it able to be forcibly enabled/disabled with a -D option?
It's looking to me like the build system now checks for wayland but doesn't care if it's there or not, and doesn't actually use it at build time in either case.
Can you confirm that?
The bug has been referenced in the following commit(s):
Author: Ben Kohler <email@example.com>
AuthorDate: 2021-07-09 14:33:29 +0000
Commit: Ben Kohler <firstname.lastname@example.org>
CommitDate: 2021-07-09 14:33:59 +0000
net-misc/remmina: remove (seemingly) unneeded wayland dep
Remmina checks for wayland during configure but doesn't seem to care
whether it's present or not, and the binaries do not link to wayland in
Package-Manager: Portage-3.0.20, Repoman-3.0.3
Signed-off-by: Ben Kohler <email@example.com>
net-misc/remmina/remmina-1.4.20.ebuild | 1 -
1 file changed, 1 deletion(-)
(In reply to Ben Kohler from comment #4)
> It's looking to me like the build system now checks for wayland but doesn't
> care if it's there or not, and doesn't actually use it at build time in
> either case.
> Can you confirm that?
I'm maintaining my own version, that doesn't require wayland as a mandatory dependency, but only if the USE flag is set.