dunst and wayland dependency

13 May 2025, 19:17:03

i know wayland is becoming the default diplay environment, but at moment Xorg is still alive. Why wayland must be a dependency for dunst? It should be [wayland | xorg]

Re: dunst and wayland dependency

Reply #1 – 13 May 2025, 22:32:48

Unfortunately that is not possible; it would required building Dunst in 2 variations: one without Wayland and the other without X11. This will result in packages with mutex installations which is not an option for us as there are users that need both. You do of course have the option to build Dunst without Wayland support yourself.

artist

Re: dunst and wayland dependency

Reply #2 – 13 May 2025, 22:43:12

You're right (about Xorg) and I hope you're wrong (about wayland becoming default).

Dunst, or any other package supporting both options, would have to be written differently in order not to depend on the presense of both libraries (use dlopen instead of being directly linked). This is clumsy and more work, so it's seldom done. And Artix ships packages that suite most people's needs.

At least wayland is small. Otherwise I'd be looking into a wayland-dummy package.

Code: [Select]

$ pacman -Qi wayland | grep Req
Required By     : gst-plugins-base-libs  gtk3  libva  mesa  mpv

This is one of the many unfortunate developments going on. It's what happened with dbus. I already forget what supposed problem that piece of crap was concocted to solve. I also have a libpulse package installed for the same reason even though I would never touch pulseaudio.

I liked using Gentoo in that I didn't have extra junk installed. But that was a lot of compiling... Extra baggage is the price of ease.