From: Sebastian Pipping <sebastian@pipping.org>
To: Maxime Devos <maximedevos@telenet.be>, guix-devel@gnu.org
Subject: Re: Expat 2.3.0 has been released
Date: Sun, 9 May 2021 14:53:09 +0200 [thread overview]
Message-ID: <06caf5b8-aa84-d2dd-9fa7-5bb35846194c@pipping.org> (raw)
In-Reply-To: <565eaa11163d5bc416387217ca8c6d6718608246.camel@telenet.be>
Hi Maxime,
On 09.05.21 11:17, Maxime Devos wrote:
> I see Leo Prikler has already sent a patch (48304@debbugs.gnu.org).
yes, thanks for you interest in the topic.
On 09.05.21 11:12, Maxime Devos wrote:
> According to "guix refresh -l", simply updating expat would entail rebuilding 6031
> packages. This can be avoided is v2.4.0 is binary compatible with v2.2.9.
> Is this the case?
The short answer is: there is no break of ABI.
A longer answer would include that the next release will also be hiding
a previously exposed internal symbol by the name
"_INTERNAL_trim_to_complete_utf8_characters". I don't consider that an
ABI break but we'll probably find someone who does, on a technical level.
The related soversions are:
2.2. 9 = 7:11:6 -> libexpatso.1.6.11 (GUIX today)
2.2.10 = 7:12:6 -> libexpatso.1.6.12
2.3. 0 = 8: 0:7 -> libexpatso.1.7.0 (GUIX W.I.P.)
2.4. 0 = 9: 0:8 -> libexpatso.1.8.0 (upcoming)
I wish related tool https://verbump.de/ was more widely known.
Best
Sebastian
next prev parent reply other threads:[~2021-05-09 12:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 20:27 Expat 2.3.0 has been released Sebastian Pipping
2021-05-08 16:00 ` Sebastian Pipping
2021-05-09 9:12 ` Maxime Devos
2021-05-09 9:17 ` Maxime Devos
2021-05-09 12:53 ` Sebastian Pipping [this message]
2021-05-09 14:07 ` Leo Famulari
2021-05-09 14:23 ` Sebastian Pipping
2021-05-09 14:32 ` Leo Famulari
2021-05-09 14:25 ` Maxime Devos
2021-05-09 22:07 ` Marius Bakke
2021-05-09 22:23 ` Sebastian Pipping
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=06caf5b8-aa84-d2dd-9fa7-5bb35846194c@pipping.org \
--to=sebastian@pipping.org \
--cc=guix-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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://git.savannah.gnu.org/cgit/guix.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).