From: Eli Schwartz <eschwartz@archlinux.org>
To: git@vger.kernel.org
Subject: gitattributes export-subst and software versioning
Date: Sun, 24 Jan 2021 19:32:17 -0500 [thread overview]
Message-ID: <7418f1d8-78c2-61a7-4f03-62360b986a41@archlinux.org> (raw)
Periodically, I wonder if there is some better way for managing tagged
releases for software in git. Current state of the art seems to be
"write a custom Makefile that takes a version and seds out the existing
version, then runs git tag for you". Inelegant solutions also abound;
people release code that does not build properly unless you build it
from a git checkout so it can run git describe. (There are half a dozen
individually popular but mutually exclusive python ecosystems for this,
in fact, all of them varying degrees of broken.)
git does have a way to automatically insert metadata via the
export-subst attribute on a file, but it's very awkward to use and you
cannot get much info out of it.
# get tags into a file, only on exact match:
$ cat VERSION
$Format:%d$
$Format:%D$
$ git archive HEAD | bsdtar -xOf - VERSION
(HEAD -> master, tag: 1.0)
HEAD -> master, tag: 1.0
With sufficient regex, you can get a release out of this, but it doesn't
work if you try getting an autogenerated tarball for a commit that isn't
exactly a release.
$ git commit --allow-empty -m ...
$ git archive HEAD | bsdtar -xOf - VERSION
(HEAD -> master)
HEAD -> master
I think it would be much, much nicer if there was a format placeholder
for git describe.
It doesn't even need option support -- the default output in most cases
could be a replacement for or fall back to existing invocations of the
"git" program, followed by post-processing with e.g. "sed".
However, the existence of current pretty formats such as %C() or
%(trailer:options) implies that options could be passed in a
git-describe format too. e.g. %(describe:--long --tags --match="v*")
Thoughts?
--
Eli Schwartz
Arch Linux Bug Wrangler and Trusted User
next reply other threads:[~2021-01-25 0:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 0:32 Eli Schwartz [this message]
2021-02-08 19:46 ` gitattributes export-subst and software versioning René Scharfe
2021-02-08 22:41 ` Junio C Hamano
2021-02-09 0:19 ` Eli Schwartz
2021-02-09 20:42 ` Junio C Hamano
2021-02-14 10:04 ` René Scharfe
2021-02-14 10:04 ` René Scharfe
2021-02-14 10:04 ` [PATCH 1/2] pretty: add %(describe) René Scharfe
2021-02-14 10:10 ` [PATCH 2/2] pretty: add merge and exclude options to %(describe) René Scharfe.
2021-02-17 18:31 ` Jeff King
2021-02-28 11:22 ` René Scharfe.
2021-02-28 15:41 ` Ævar Arnfjörð Bjarmason
2021-03-02 16:00 ` René Scharfe.
2021-03-06 16:18 ` René Scharfe.
[not found] ` <xmqqy2f6rc8f.fsf@gitster.c.googlers.com>
2021-03-02 16:00 ` René Scharfe.
[not found] ` <xmqqsg5uletz.fsf@gitster.g>
2021-02-28 11:22 ` René Scharfe.
2021-02-16 5:04 ` [PATCH 1/2] pretty: add %(describe) Eli Schwartz
2021-02-16 13:00 ` Ævar Arnfjörð Bjarmason
2021-02-16 17:13 ` René Scharfe.
2021-02-16 18:44 ` Junio C Hamano
2021-02-17 0:47 ` Ævar Arnfjörð Bjarmason
2021-02-28 11:22 ` René Scharfe.
[not found] ` <xmqq35xesqzk.fsf@gitster.c.googlers.com>
2021-03-02 16:00 ` René Scharfe.
2021-02-17 0:58 ` Ævar Arnfjörð Bjarmason
2021-02-17 18:12 ` Junio C Hamano
2021-02-28 11:22 ` René Scharfe.
[not found] ` <xmqq7dmqsr72.fsf@gitster.c.googlers.com>
2021-03-02 16:00 ` René Scharfe.
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7418f1d8-78c2-61a7-4f03-62360b986a41@archlinux.org \
--to=eschwartz@archlinux.org \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).