From: Dmitry Marakasov <amdmi3@amdmi3.ru>
To: bug-gnulib@gnu.org
Subject: Versioned releases
Date: Thu, 4 Jun 2020 18:41:44 +0300 [thread overview]
Message-ID: <20200604154144.GB11553@hades.panopticon> (raw)
Hi!
Despite that gnulib homepage says "Gnulib does not make releases.
It is intended to be used at the source level." gnulib is in fact
packaged in quite a lot of distributions:
https://repology.org/project/gnulib/versions
Note that since there are no official versions maintainers have to
invent versioning schemes which include "0", multiple date based and
commit number based formats.
There are known vulnerabilities for gnulib which also have to use
something version-like to describe which gnulib versions are affected
(these use dates in YYYY-MM-DD format):
https://nvd.nist.gov/vuln/detail/CVE-2017-7476
https://nvd.nist.gov/vuln/detail/CVE-2018-17942
Note that it's impossible to match these against package versions due
to inconsistent versioning scheme.
So as you can see, even though there are no official versioned releases,
people have to invent and use these to refer to specific gnulib commit
ranges, and not having any consistency in these schemes results in e.g.
inability to report vulnerable packages.
So I suggest to fix this by introducing any kind of upstream versioning.
Versions don't even need to have any meaning or be tied to specific events
such as API breakages or adding new features (however using semver would
probably be most useful for consumers), there's just need to be an official
versioning scheme, and some eventual releases so people don't have to
reside to inventing snapshot schemes.
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amdmi3@amdmi3.ru ..: https://github.com/AMDmi3
next reply other threads:[~2020-06-04 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 15:41 Dmitry Marakasov [this message]
2020-06-04 18:19 ` Versioned releases 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
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=20200604154144.GB11553@hades.panopticon \
--to=amdmi3@amdmi3.ru \
--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).