Bogus output for gio, pango, and many other gtk related packages #136
Labels
Comments
peti
changed the title
peti
added a commit
that referenced
this issue
Jan 22, 2015
The post-process hook filters any package from pkgconfigDepends that is also part of buildDepends. In other words, if some package depends on the Haskell library "glib", then we filter "glib" from pkgconfigDepends. As a result, the bogus resolver in "hackage2nix" won't fire. Of course, this means that the system library is now missing from those builds that had their pkgconfigDepends stripped. We counter this by adding the appropriate system package to the propagatedBuildInputs field of the their corresponding Haskell library. For example, the Haskell package "glib" exports the system library "glib" to all its users -- so these users don't have to depend on it anymore. The real solution is to fix the resolver, of course, but this change will hopefully fix a number of builds *right now* without much of an effort to do the right thing(tm).
peti
added a commit
to NixOS/nixpkgs
that referenced
this issue
Jan 22, 2015
This commit also implements the second part of the NixOS/cabal2nix@4f603d1 hack to work around NixOS/cabal2nix#136 Fixes #5902.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Cabal file for
giospecifies a pkgconfig dependency ongio. However, that name gets re-written toglibbecausegiois part ofglibin Nixpkgs. So we end up in a situation where there generated expression has a dependency on both the Haskell packageglibinbuildDependsand the system packageglibinpkgconfigDepends. Since both have the same name, we cannot pass both!haskell2nixdecides that theglibreference to the Haskell package set will be found automatically bycallPackageand does nothing for that. For the pkgconfig reference, it generates an override to setglib = pkgs.glib. The net result is that the Haskell package reference will not be included and the build fails as reported in NixOS/nixpkgs#5863.The text was updated successfully, but these errors were encountered: