@peti Thanks for cleaning this up and merging it in.

I saw your additional commit in 3ab6627, and your message about this here: #76883 (comment).

I'm wondering if you had any policies in mind for when we allow/disallow things to be added default-package-overrides?

For instance, #76883 is a problem because it appears that a newer version of gi-gdkx11 causes taffybar to fail to build. I think taffybar is used by a non-trivial number of users, so ideally we should try to keep it working. (The same way we try to keep things like cabal-install, stack, xmonad, etc working.)

#76883 could be solved by adding gi-gdkx11 to default-package-overrides. Or, it could be solved by adding gi-gdkx11 to extra-packages, getting hackage2nix to generate gi-gdkx11_3_0_9, and overriding all the derivations that need it (like taffybar).

Do you have a preference for how to handle these types of problems?

ping @peti. I'd like to come up with a loose set policies for when we allow/disallow things to be added to default-package-overrides.

Although for now I'd be completely happy with that policy being "take it on a case-by-case basis".

I believe that we'll have to judge it case by case. Personally, I would add overrides to default-package-overrides if the change fixes many packages and breaks only few. :-)