Sunday, March 01, 2026

Re: x11/dunst - add wayland FLAVOR?

I don't have strong opinions on wayland support being a flavor or not, but I
assumed that there were reasons to disable wayland in the first place ...

Having said that, this is the remaining puzzle piece for me to switch from my
old herbstluftwm setup to niri as my daily driver, so I hope one way or another,
that we'll get wayland support into dunst ;-)

On 3/1/26 6:37 PM, Tobias Heider wrote:
> On Sun, Mar 01, 2026 at 02:57:08PM +0100, Volker Schlecht wrote:
>> To use dunst on niri, we need wayland support built in (the non-wayland version
>> works with XWayland under wayland/sway, but with xwayland-satellite as used by
>> niri, notifications appear as regular windows with decorations and all.
>>
>> Therefore I'd like to propose a wayland FLAVOR for x11/dunst.
>>
>> What do you think?
>>
>
> Works here. I have no partiuclar opinion on making wayland support
> a flavor but the diff is ok with me if Timo agrees.
>
>> Index: Makefile
>> ===================================================================
>> RCS file: /cvs/ports/x11/dunst/Makefile,v
>> retrieving revision 1.20
>> diff -u -p -r1.20 Makefile
>> --- Makefile 31 Dec 2025 14:23:22 -0000 1.20
>> +++ Makefile 1 Mar 2026 13:48:36 -0000
>> @@ -10,6 +10,8 @@ HOMEPAGE= https://dunst-project.org/
>>
>> MAINTAINER = Timo Myyra <timo.myyra@bittivirhe.fi>
>>
>> +FLAVORS = wayland
>> +FLAVOR ?=
>> # BSD
>> PERMIT_PACKAGE = Yes
>>
>> @@ -44,8 +46,14 @@ MAKE_FLAGS = PREFIX="${PREFIX}" \
>> SYSCONFDIR="/etc" \
>> BASHCOMPLETIONDIR="${LOCALBASE}/share/bash-completion/completions" \
>> FISHCOMPLETIONDIR="${LOCALBASE}/share/fish/vendor_completions.d" \
>> - ZSHCOMPLETIONDIR="${LOCALBASE}/share/zsh/site-functions" \
>> - WAYLAND=0
>> + ZSHCOMPLETIONDIR="${LOCALBASE}/share/zsh/site-functions"
>> +
>> +.if ${FLAVOR:Mwayland}
>> +LIB_DEPENDS += wayland/wayland
>> +WANTLIB += wayland-client wayland-cursor
>> +.else
>> +MAKE_FLAGS += WAYLAND=0
>> +.endif
>>
>> pre-configure:
>> ${SUBST_CMD} ${WRKSRC}/docs/dunst.1.pod.in \
>

No comments:

Post a Comment