From: Paul Eggert <eggert@cs.ucla.edu>
To: Bruno Haible <bruno@clisp.org>,
bug-gnulib@gnu.org, Simon Josefsson <simon@josefsson.org>
Subject: Re: [PATCH] announce-gen: Mention git commit in release announcement.
Date: Sun, 12 May 2024 13:47:25 -0700 [thread overview]
Message-ID: <7fd3cab0-fd09-4269-8a06-747ddbfd9edb@cs.ucla.edu> (raw)
In-Reply-To: <4217409.1IzOArtZ34@nimes>
On 2024-05-12 12:50, Bruno Haible wrote:
> Your real goal, which is — AFAIU — to allow distros to discard part
> or all of the tarball and to redo the packaging work done by the release
> manager in a different way, would be better served with a
> 1) machine-readable file,
> 2) somewhere in or in the vicinity of the tarball.
Although that's a good goal to have (see below), it's reasonably
ambitious. For example, the tool lists we've been mentioning are
incomplete, partly due to indirect dependencies (no glibc?) and partly
not (no coreutils?) and it will be a pain to complete them (no firmware
IDs? no motherboard or CPU IDs? you get the picture...). So I suspect
that having an intermediate goal could be worthwhile.
>
> In other words, if you really want to go this way — against the advice that
> I gave you above —, better replace the two lines with:
>
> This release is based on the inetutils git, available at
> https://git.savannah.gnu.org/git/inetutils.git
> commit 524d4b6934db12b9f43be410d2f201fdb40cfc97, also labelled v1.42.
This is good advice. It's similar to wording I use in announcements of
TZDB distributions (e.g.,
<https://mm.icann.org/pipermail/tz-announce/2024-February/000081.html>).
For what it's worth, those TZDB announcements have always intended to be
human readable but various downstream projects parse the text and grab
checksums and signatures and whatnot. The pull of automation is indeed
strong, and your advice about going for automation is good.
prev parent reply other threads:[~2024-05-12 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 15:42 [PATCH] announce-gen: Mention git commit in release announcement Simon Josefsson via Gnulib discussion list
2024-05-12 16:27 ` Jim Meyering
2024-05-12 16:46 ` Paul Eggert
2024-05-12 19:50 ` Bruno Haible
2024-05-12 20:47 ` Paul Eggert [this message]
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: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7fd3cab0-fd09-4269-8a06-747ddbfd9edb@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--cc=simon@josefsson.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.
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).