From: Patrick Steinhardt <ps@pks.im>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Kyle Lippincott <spectral@google.com>
Subject: Re: [PATCH v2 1/5] GIT-VERSION-GEN: fix overriding version via environment
Date: Fri, 20 Dec 2024 17:16:42 +0100 [thread overview]
Message-ID: <Z2WYajwW-Isxmzwz@pks.im> (raw)
In-Reply-To: <20241220155223.GA152570@coredump.intra.peff.net>
On Fri, Dec 20, 2024 at 10:52:23AM -0500, Jeff King wrote:
> On Fri, Dec 20, 2024 at 01:22:45PM +0100, Patrick Steinhardt wrote:
>
> > diff --git a/GIT-VERSION-GEN b/GIT-VERSION-GEN
> > index de0e63bdfbac263884e2ea328cc2ef11ace7a238..27f9d6a81f77248c652649ae21d0ec51b8f2d247 100755
> > --- a/GIT-VERSION-GEN
> > +++ b/GIT-VERSION-GEN
> > @@ -29,7 +29,10 @@ export GIT_CEILING_DIRECTORIES
> >
> > # First see if there is a version file (included in release tarballs),
> > # then try git-describe, then default.
> > -if test -f "$SOURCE_DIR"/version
> > +if test -n "$GIT_VERSION"
> > +then
> > + VN="$GIT_VERSION"
> > +elif test -f "$SOURCE_DIR"/version
>
> Hmm. If $GIT_VERSION is set, then we set $VN here...
>
> > -GIT_VERSION=$(expr "$VN" : v*'\(.*\)')
> > +# Only strip leading `v` in case we have derived VN manually. Otherwise we
> > +# retain whatever the user has set in their environment.
> > +if test -z "$GIT_VERSION"
> > +then
> > + GIT_VERSION=$(expr "$VN" : v*'\(.*\)')
> > +fi
>
> ...but later we ignore $VN completely.
>
> So it would work equally well with the first hunk dropped completely.
> However, having an entry in the cascading if/else does mean that we
> short-circuit the effort to run git-describe, etc.
>
> I don't think the old code ever did that (we'd generate the Makefile
> snippet in GIT-VERSION-FILE, read it back, and then make would still
> override the value from the snippet).
>
> So I dunno. I like keeping things simple, but I also like skipping
> unnecessary code, too. Maybe if the top hunk were:
>
> if test -n "$GIT_VERSION"
> then
> : do nothing, we will use this value verbatim
> elif ...
>
> that would make the intended flow more obvious.
>
> There are probably other ways to structure it, too. The whole $VN thing
> could be inside the:
>
> if test -z "$GIT_VERSION"
>
> block. Or alternatively, if each block of the if/else just ran expr and
> set $GIT_VERSION itself (perhaps with a one-liner helper function) then
> we wouldn't need $VN at all.
>
> I don't know how much trouble it's worth to refactor all this. Mostly I
> was just surprised to see the first hunk at all in this version.
I think wrapping it all in `if test -z "$GIT_VERSION"` would be best. I
was thinking about whether to do that refactoring, but I shied away from
it due to the required reindentation. But I agree that the end result is
a bit on the awkward side.
You know, let me send another iteration where I just do it, now that
we're two having the same thought.
Patrick
next prev parent reply other threads:[~2024-12-20 16:18 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 15:53 [PATCH 0/2] GIT-VERSION-GEN: fix overriding values Patrick Steinhardt
2024-12-19 15:53 ` [PATCH 1/2] GIT-VERSION-GEN: fix overriding version via environment Patrick Steinhardt
2024-12-19 18:49 ` Junio C Hamano
2024-12-20 7:34 ` Jeff King
2024-12-20 8:45 ` Patrick Steinhardt
2024-12-20 8:56 ` Jeff King
2024-12-20 9:31 ` Patrick Steinhardt
2024-12-20 11:17 ` Jeff King
2024-12-20 12:22 ` Patrick Steinhardt
2024-12-19 15:53 ` [PATCH 2/2] GIT-VERSION-GEN: fix overriding GIT_BUILT_FROM_COMMIT and GIT_DATE Patrick Steinhardt
2024-12-19 21:19 ` Kyle Lippincott
2024-12-19 21:59 ` Junio C Hamano
2024-12-20 7:37 ` Jeff King
2024-12-20 15:04 ` Junio C Hamano
2024-12-20 12:22 ` [PATCH v2 0/5] GIT-VERSION-GEN: fix overriding values Patrick Steinhardt
2024-12-20 12:22 ` [PATCH v2 1/5] GIT-VERSION-GEN: fix overriding version via environment Patrick Steinhardt
2024-12-20 15:52 ` Jeff King
2024-12-20 16:16 ` Patrick Steinhardt [this message]
2024-12-20 16:17 ` Junio C Hamano
2024-12-20 16:23 ` Patrick Steinhardt
2024-12-20 12:22 ` [PATCH v2 2/5] GIT-VERSION-GEN: fix overriding GIT_BUILT_FROM_COMMIT and GIT_DATE Patrick Steinhardt
2024-12-20 12:22 ` [PATCH v2 3/5] Makefile: drop unneeded indirection for GIT-VERSION-GEN outputs Patrick Steinhardt
2024-12-20 15:53 ` Jeff King
2024-12-20 12:22 ` [PATCH v2 4/5] Makefile: respect build info declared in "config.mak" Patrick Steinhardt
2024-12-20 15:54 ` Jeff King
2024-12-20 16:47 ` Patrick Steinhardt
2024-12-20 17:51 ` Jeff King
2024-12-20 18:02 ` Patrick Steinhardt
2024-12-20 18:18 ` Patrick Steinhardt
2024-12-20 18:24 ` Jeff King
2024-12-20 18:39 ` Patrick Steinhardt
2024-12-20 19:07 ` Patrick Steinhardt
2024-12-28 19:43 ` Jeff King
2024-12-20 12:22 ` [PATCH v2 5/5] meson: add options to override build information Patrick Steinhardt
2024-12-20 15:56 ` [PATCH v2 0/5] GIT-VERSION-GEN: fix overriding values Jeff King
2024-12-20 19:44 ` [PATCH v3 0/6] " Patrick Steinhardt
2024-12-20 19:44 ` [PATCH v3 1/6] Makefile: stop including "GIT-VERSION-FILE" in docs Patrick Steinhardt
2024-12-20 19:44 ` [PATCH v3 2/6] Makefile: drop unneeded indirection for GIT-VERSION-GEN outputs Patrick Steinhardt
2024-12-20 19:44 ` [PATCH v3 3/6] Makefile: introduce template for GIT-VERSION-GEN Patrick Steinhardt
2024-12-20 19:44 ` [PATCH v3 4/6] GIT-VERSION-GEN: fix overriding GIT_VERSION Patrick Steinhardt
2024-12-20 21:50 ` Junio C Hamano
2024-12-21 10:30 ` Patrick Steinhardt
2024-12-20 19:44 ` [PATCH v3 5/6] GIT-VERSION-GEN: fix overriding GIT_BUILT_FROM_COMMIT and GIT_DATE Patrick Steinhardt
2024-12-20 19:44 ` [PATCH v3 6/6] meson: add options to override build information Patrick Steinhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z2WYajwW-Isxmzwz@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=spectral@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).