···3030 - skopeo
3131 - nix
3232 - postgresql_15
3333+ - postgresql_15.pg_config # pg_config is a separate output in nixpkgs 25.05+ / unstable
3334 - libffi
3435 - openjpeg
3536 - pango
···140141 # -----------------------------------------------------------------
141142 # psycopg_c build fix
142143 #
143143- # pip's PEP 517 build-isolation spawns an isolated subprocess with
144144- # its own PATH overlay (/tmp/pip-build-env-*/overlay/…) that
145145- # shadows /usr/bin, /usr/local/bin, and any PATH we export here.
146146- # The metadata-generation phase calls `pg_config` as a bare command
147147- # via subprocess.run(["pg_config", ...]) using the ambient PATH —
148148- # NOT the PG_CONFIG env var — so symlinks and exports alone fail.
144144+ # In nixpkgs 25.05+ / unstable, pg_config was split into a separate
145145+ # output (postgresql_15.pg_config). We list it explicitly in the
146146+ # dependencies so it's on PATH automatically via the Nix profile.
149147 #
150150- # Fix: use --no-build-isolation for psycopg[c] so the build runs
151151- # directly in our environment where pg_config is on PATH and
152152- # PG_CONFIG is exported. We pre-install the build deps (setuptools,
153153- # wheel) so the non-isolated build succeeds.
148148+ # We still use --no-build-isolation for psycopg[c] because pip's
149149+ # PEP 517 build-isolation spawns an isolated subprocess with its
150150+ # own PATH overlay that can shadow the profile PATH. Building
151151+ # without isolation ensures our env vars (PG_CONFIG, PATH,
152152+ # LDFLAGS, CPPFLAGS) are visible to the build backend.
154153 # -----------------------------------------------------------------
155154 echo "=== Locating pg_config ==="
156155157156 PG_CONFIG_BIN=""
158157159159- # Try 1: already on PATH
158158+ # Try 1: already on PATH (expected — postgresql_15.pg_config is in dependencies)
160159 PG_CONFIG_BIN="$(command -v pg_config 2>/dev/null || true)"
161160162161 # Try 2: common Nix profile locations