This file is generated automatically using hackage2nix. There we have to pick an attribute based on:

    pkgconfig-depends: x11 >= 1.6

I suspect that xlibsWrapper is chosen, since a lot of packages declare x11 when they want more than just libX11.

If you care about this strongly, you can override this in configuration-nix.nix by way of passing xorg.libX11 as xlibsWrapper.

This PR can't be merged as is, since the changes would be rolled back. The other question is, of course, why does this change matter?

This file is generated automatically using hackage2nix.

Oh, that was not obvious from commits to this file. The top-level comment also does not say what was used to generate the file. cabal2nix is a useful hint. Thanks.

There we have to pick an attribute based on:

    pkgconfig-depends: x11 >= 1.6

I suspect that xlibsWrapper is chosen, since a lot of packages declare x11 when they want more than just libX11.

There are exactly 3 haskell packages that use xlibsWrapers in nixpkgs: gi-xlib, greenclip, gtk-traymanager. Does not sound like a lot. At least gi-xlib just uses libX11. I'll have a look at the rest, but I don't expect anything different.

If you care about this strongly, you can override this in configuration-nix.nix by way of passing xorg.libX11 as xlibsWrapper.

This PR can't be merged as is, since the changes would be rolled back.

I'll have a look at cabal2nix to generate libX11 depends.

The other question is, of course, why does this change matter?

I don't think there is a use case for xlibsWrapper today at all apart from confusing people by it's very existence. I think it was added as a convenience package right after the modular xorg split to postpone fixing dependencies. #194054 has a few more examples of packages that pulled it in for no specific reason and cleaned up since.

Proposed NixOS/cabal2nix#589 to use libX11 consistently.

Proposed NixOS/cabal2nix#590 to hint at the tool that generates the file.

Closing in favour of 5bc95ac