From: Bernhard Voelker <mail@bernhard-voelker.de>
To: Bruno Haible <bruno@clisp.org>, bug-gnulib@gnu.org
Cc: Dmitry Marakasov <amdmi3@amdmi3.ru>
Subject: Re: Versioned releases
Date: Fri, 5 Jun 2020 01:10:23 +0200 [thread overview]
Message-ID: <5c623e40-8318-91ca-48a1-cb2b8cd238ce@bernhard-voelker.de> (raw)
In-Reply-To: <1941801.zvzjLHy5AZ@omega>
On 2020-06-04 20:19, Bruno Haible wrote:
> Indeed e.g. Debian has a gnulib "package":
> https://packages.debian.org/sid/all/gnulib/filelist
>
> But I think it's a red herring, since basically no one is using gnulib
> this way.
I agree, it's not really useful: e.g. I'm using openSUSE:Tumbleweed,
a rolling release with almost the latest and greatest. But still,
the version of it is already >260 commits behind (from 2020-02-16).
Well, the 'gnulib-docs' package integrates well, but some content
is already outdated - especially the newer, interesting parts.
I guess that other, non-rolling distros come with much older and
therefore even more useless versions.
> You mean, a distributor wants to determine which of the coreutils,
> findutils, gawk, gettext, etc. package use the Gnulib before 2018-09-23?
> This is nontrivial, but not because Gnulib does not have a version
> number, but because it's shipped as a source-code library - something that
> we don't want to change.
Well, the projects using gnulib (via git submodule) could at least generate
the 'git describe' value into their NEWS file or other documentation.
And gnulib could provide helpers for that.
Still, that wouldn't help in the case the packager adds a downstream
patch for gnulib files. Well, that same patch could include add a note
for it in the docs as well.
Have a nice day,
Berny
next prev parent reply other threads:[~2020-06-04 23:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 15:41 Versioned releases Dmitry Marakasov
2020-06-04 18:19 ` Bruno Haible
2020-06-04 19:29 ` Dmitry Marakasov
2020-06-04 21:29 ` Bruno Haible
2020-06-05 12:15 ` Paul Smith
2020-06-04 19:46 ` Paul Smith
2020-06-04 20:11 ` Dmitry Marakasov
2020-06-04 21:16 ` Paul Smith
2020-06-04 23:10 ` Bernhard Voelker [this message]
2020-06-04 23:24 ` Bruno Haible
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=5c623e40-8318-91ca-48a1-cb2b8cd238ce@bernhard-voelker.de \
--to=mail@bernhard-voelker.de \
--cc=amdmi3@amdmi3.ru \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.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).