From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Josef Šimánek <josef(dot)simanek(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Git revision in tarballs |
Date: | 2021-07-15 14:35:41 |
Message-ID: | 3618220.1626359741@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Putting it in the tarball making script certainly works for me,
> though, if that's what people prefer. And that does away with the
> "clean" part as that one blows away the whole directory between each
> run.
Actually, we *have* to do it over there, because what that script
does is
# Export the selected git ref
git archive ${i} | tar xf - -C pgsql
cd pgsql
./configure
# some irrelevant stuff
make dist
So there's no .git subdirectory in the directory it runs "make dist"
in. Now maybe it'd work anyway because of the GIT_DIR environment
variable, but what I think is more likely is that the file would
end up containing the current master-branch HEAD commit, whereas
the thing we actually want to record here is ${i}.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ranier Vilela | 2021-07-15 14:45:39 | Re: [PATCH] Use optimized single-datum tuplesort in ExecSort |
Previous Message | Paul A Jungwirth | 2021-07-15 14:29:42 | Re: SQL:2011 PERIODS vs Postgres Ranges? |