Re: [PATCH v2 1/5] GIT-VERSION-GEN: fix overriding version via environment

On Fri, Dec 20, 2024 at 01:22:45PM +0100, Patrick Steinhardt wrote:

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.

-Peff