nixpkgs/pkgs
Spencer Baugh 46f2b49b44 pythonPackages.pkgconfig: use same setupHook as pkgconfig
This setupHook is necessary for actually using pkgconfig. Without this
setupHook, you need to put both pythonPackages.pkgconfig and pkgconfig
into your buildInputs, just to get the setuphook of the latter.

Previously, pythonPackages.pkgconfig depended on pkgconfig as a
propagatedBuildInput, so this setupHook was propagated down to
dependents. That was changed to a regular nativeBuildInput, so now
this setupHook change is necessary for packages to only depend on
pythonPackages.pkgconfig.

A possible alternative is extracting out a common pkgconfigHook
package and having both pythonPackages.pkgconfig and pkgconfig depend
on that with propagatedBuildInputs. That might be necessary to avoid
the buildHook running twice?
2019-02-17 14:40:51 +01:00
..
applications dosage: fix build 2019-02-17 14:40:51 +01:00
build-support Merge master into staging 2019-02-14 11:35:50 +01:00
common-updater
data
desktops
development pythonPackages.pkgconfig: use same setupHook as pkgconfig 2019-02-17 14:40:51 +01:00
games Merge master into staging 2019-02-14 11:35:50 +01:00
misc Merge master into staging 2019-02-14 11:35:50 +01:00
os-specific Merge master into staging 2019-02-14 11:35:50 +01:00
servers home-assistant: fix pinned dependencies' builds 2019-02-17 14:40:50 +01:00
shells
stdenv
test
tools awscli: 1.16.90 -> 1.16.104 2019-02-17 14:40:51 +01:00
top-level python.pkgs.soupsieve: init at 1.7.3 2019-02-17 14:40:48 +01:00