summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorWolfgang Walther <walther@technowledgy.de>2024-03-04 21:26:50 +0100
committerWolfgang Walther <walther@technowledgy.de>2024-08-23 21:37:49 +0200
commit435f51c37faf74375134dfbd7c5a4560da2a9ea7 (patch)
tree2b92c04c98786507eeb62b88c65220a87c1895ae /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent77977286d80c9bfb77cbf80989d41c59d66dccf8 (diff)
postgresql: split dev output
This splits a dev output to make the default output not depend on any build dependencies anymore. This also avoids removing references from pgxs' Makefile this way, which should, at least theoretically, be good to build extensions via pgxs, making sure they use the same tooling. ecpg is the "embedded SQL C preprocessor", which is certainly a dev tool. Most important, for closure size anyway, is to move pg_config to the dev output, since it retains paths to all the other outputs. The only thing with references to the dev output remaining is then the postgres binary itself. It contains all the output paths, because it shows those in the pg_config system view. There is no other way than to nuke those references to avoid circular dependencies between outputs - and blowing up closure size again.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions