summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorWolfgang Walther <walther@technowledgy.de>2025-05-17 14:19:35 +0200
committerWolfgang Walther <walther@technowledgy.de>2025-06-24 10:01:07 +0200
commit9a146d12448f32d549825dc71b7d1922c2522e35 (patch)
tree24845b13cc77cf31530623a2185a81f33543db84 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent8ad467f6d5f3533c961e456a43948373f41a98da (diff)
postgresql.withPackages.pg_config: fix paths
Previously, pg_config would report the paths of the underlying postgresql derivation and not the paths of the buildEnv that postgresql.withPackages creates. That's a problem when users of pg_config use it to find PostgreSQL's sharedir, in which they'd like to find the extensions added via withPackages. Those are only linked into the created buildEnv, but not available in the postgresql derivation. By providing our own nix-support/pg_config.env file, we can swap out those paths. We also do the same for the -man output, because this output is linked into buildEnv as well. Other paths, which are not available in the buildEnv environment, will still link to the original postgresql derivation. Win-win!
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions