Wolfgang Walther 154215cfd8 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.		2024-04-04 08:41:18 +02:00
..
less-is-more.patch	postgresql: clean up patches	2024-04-04 08:41:18 +02:00
locale-binary-path.patch	postgresql: clean up patches	2024-04-04 08:41:18 +02:00
paths-for-split-outputs.patch	postgresql: rename patches	2024-04-04 08:41:18 +02:00
paths-with-postgresql-suffix.patch	postgresql: rename patches	2024-04-04 08:41:18 +02:00
relative-to-symlinks-16+.patch	postgresql: rename patches	2024-04-04 08:41:18 +02:00
relative-to-symlinks.patch	postgresql: rename patches	2024-04-04 08:41:18 +02:00
socketdir-in-run-13+.patch	postgresql: rename patches	2024-04-04 08:41:18 +02:00
socketdir-in-run.patch	postgresql: clean up patches	2024-04-04 08:41:18 +02:00
specify_pkglibdir_at_runtime.patch	postgresql: clean up patches	2024-04-04 08:41:18 +02:00