make pgtle PGTLE_VERSION=1.5.0+
make pgtle PGXNTOOL_PGTLE_VERSION=1.5.0
Set PGTLE_VERSION on the command line to limit generation to the single version range that value falls into, instead of every known range:
Set PGXNTOOL_PGTLE_VERSION on the command line to limit generation to the single version range that value falls into, instead of every known range:
make pgtle PGTLE_VERSION=1.5.0+
make pgtle PGXNTOOL_PGTLE_VERSION=1.5.0
.control file’s default_version) will be automatically regenerated when you run make, but other version files you create manually will be preserved.
+DATA (the PGXS variable controlling what make install actually installs) is seeded by pgxntool with $(wildcard sql/--.sql), so PGXS installs whatever version-specific and upgrade files exist under sql/ when DATA is evaluated.
If your extension generates its versioned SQL from another source (e.g. a .sql.in template expanded by a custom rule) and gitignores the generated .sql, a clean make install (or make test, make all install in one invocation) can silently omit files that were only just generated during that same run. This isn’t a pattern-matching problem — the glob is correct — it’s a GNU Make quirk: wildcard caches a directory’s contents internally for the life of one make invocation, and that cache isn’t invalidated just because a recipe created new files earlier in the same run. So even though DATA is a recursively-expanded variable (re-evaluated each time it’s referenced), re-referencing it later in the same invocation can still see the stale, pre-generation listing.
Workarounds:
+Run generation and install as separate make invocations (e.g. make && make install) so the second invocation’s parse-time wildcard scan sees files the first invocation created.
List the generated files in DATA explicitly, keyed off stable names derived from your .sql.in sources (known at parse time) rather than relying on wildcard to discover the generated .sql output.
Tracked as issue #44 — pgxntool doesn’t yet have first-class support for generated versioned SQL; the ideas under discussion there (e.g. a dedicated generated-output directory pgxntool builds before installing) are a bigger design change than a one-line fix.
+Default: unset (generates every known pg_tle version range). Set on the command line to limit make pgtle to the single version range this value falls into. See pgtle.
Default: unset (generates every known pg_tle version range). Set on the command line to limit make pgtle to the single version range this value falls into. Not named PGTLE_VERSION: make auto-imports same-named environment variables, and that name collided silently with CI jobs that set a PGTLE_VERSION env var for an unrelated purpose (which pg_tle to test against). See pgtle.