Re: Git revision in tarballs

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 18:55:41
Message-ID: CABUevEzbfdOa1wg5y2bvGJVWwLj_Jy0EQbH=8kdAMZ9ORcDi6w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 15, 2021 at 4:35 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> 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}.

Hah, yeah, that certainly decides it. And I was even poking around
that script as well today, just nt at the same time :)

--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2021-07-15 19:07:19 Re: [PATCH] psql: \dn+ to show size of each schema..
Previous Message Dave Cramer 2021-07-15 18:51:53 Re: pg_upgrade does not upgrade pg_stat_statements properly