On Mon, Mar 24, 2025 at 10:31:20PM +0100, NoisyCoil wrote:
On 24/03/25 19:53, Chris Hofstaedtler wrote:
AFAIK this is exactly the point of Recommends. Not all situations
require the package, and the user must change the defaults to not
get the dependency installed.
To me "alacritty (literally) crashes on X11 without
libxkbcommon-x11-0" reads much more strongly than "not all situations
require the package". One can very well argue that not having
libxkbcommon-x11-0 installed with X11 is an unusual situation, and I
agree, but the solution then is finding out what component of the
stack is missing the dependency and adding it there.
The simple solution is probably just to do as you initially suggested -
Depends on both of them. They have pretty small dependency trees.
Even better would be doing this naturally through detection of used
symbols so library transitions are handled sanely.
So, I guess I'd refine my near term suggestion of options:
1. Adjust the packaging so dlopen isn't used, which will result in both
libraries being Depends automatically.
2. Hard-code unversioned Depends for the libraries
I'm leaning towards 1, but I'd need to investigate what that effort is.
Cheers,
--
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7 2D23 DFE6 91AE 331B A3DB
