From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Preparing to release 0.9.12
Date: Thu, 25 Jul 2013 22:08:59 -0400 [thread overview]
Message-ID: <20130726020859.GP4284@brightrain.aerifal.cx> (raw)
In-Reply-To: <20130726003851.GA20873@newbook>
On Thu, Jul 25, 2013 at 05:38:51PM -0700, Isaac wrote:
> > The so versioning will not help for C++ related things. The most
> > important use case I had in mind is that, package managers that use
> > soversions for automatic dependencies, can insert proper "require
> > version XXX or later of this .so". That is, if we built with musl X, we
> > can detect that from .so, and record it. And later ensure that musl X-1
> > will not satisfy the newly built package's dependencies. Especially
> > important when we are introducing new symbols.
>
> On Debian, there's the "symbols" system; this lists all symbols with the
> version they appeared in, and the tools look through the symbols and
> find the lowest version providing all the symbols.
>
> But as a standard rule, _added_ symbols _do_ _not_ call for a new SONAME,
> since they do not break the ABI.
Good point. In that case, it sounds like it would be wrong to have the
SONAME of musl reflect the version, no?
Rich
next prev parent reply other threads:[~2013-07-26 2:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-24 20:02 Rich Felker
2013-07-25 7:44 ` Timo Teras
2013-07-25 15:05 ` Szabolcs Nagy
2013-07-25 15:45 ` Timo Teras
2013-07-25 16:39 ` Rich Felker
2013-07-25 16:16 ` Rich Felker
2013-07-25 16:59 ` Timo Teras
2013-07-25 17:18 ` Rich Felker
2013-07-25 17:27 ` Rich Felker
2013-07-26 0:38 ` Isaac
2013-07-26 2:08 ` Rich Felker [this message]
2013-07-26 5:13 ` Timo Teras
2013-07-26 5:34 ` Rich Felker
2013-07-26 6:07 ` Timo Teras
2013-07-26 6:18 ` Rich Felker
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130726020859.GP4284@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
/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.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).