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-05 15:15:07 +0100
committerWolfgang Walther <walther@technowledgy.de>2024-04-04 08:41:18 +0200
commit154215cfd8f81f76e8a9f054ef52679564bf40c1 (patch)
treeaa64bd9066ec61d5d770e7e0a7f4ad5dfad8e538 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parent605618c2e8ba6257fd17479f76e0d08682c4bc7f (diff)
postgresql: rename patches
Trying to understand what each patch does made me come up with some more descriptive names: - Renaming the two disable-xxx patches to a common names makes it immediately clear that one replaces the other depending on version number. - findstring was really not descriptive at all. - hardcode-pgxs-path will be extended with more paths for split outputs in a later commit. Renaming here already to allow git to better track renames. Finally replacing HARDCODED_PGXS_PATH with $out/lib in the last patch, makes it easier to understand what the end result will look like when reading the patch.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions