mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Adjustments to roadmap
Date: Sun, 30 Aug 2015 00:46:54 -0400	[thread overview]
Message-ID: <20150830044654.GJ7833@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150830112128.77511bbc@r2lynx>

On Sun, Aug 30, 2015 at 11:21:28AM +0700, Рысь wrote:
> Don't you think that the snowball effect will be later in future so much
> amplified by this decision so that it will not be even able to be
> patched out? Well, then, that's why I prefer to use old stable versions
> which do not suffer from these virtual problems.

No, I don't, mainly because I don't ascribe that level of
self-importance to musl. :-) People who are using misguided features
like symbol versioning are not making the decision to do so based on
whether or not musl supports them. And there are already good reasons
to argue against use of symbol versioning aside from "it doesn't work
with musl" such as how it interacts with static linking.

As for your concern about "being unable to patch it out", if you're
running correct/matching library versions for your apps so they don't
need old symbol versions, the worst that should happen from "turning
back off" version support in musl ldso would be that libgcc_s breaks
(due to the internal use of a non-public version); then you just go
and patch libgcc_s not to do this.

If on the other hand you _do_ have mismatched library versions such
that old symbol versions are needed, then right now you've got silent
breakage with musl; if we supported versions and then you went and
patched that out, you'd just end up back where we are now, but not
with any new breakage.

Does that adequately address your concerns?

Rich


  reply	other threads:[~2015-08-30  4:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28  2:43 Rich Felker
2015-08-28  3:38 ` Khem Raj
2015-08-28  4:21   ` Rich Felker
2015-08-28  6:57     ` Вася Бойцов
2015-08-28 12:47       ` Rich Felker
2015-08-28 12:16     ` Justin Cormack
2015-08-28  7:24 ` u-wsnj
2015-08-28 11:39   ` Рысь
2015-08-28 17:18     ` Rich Felker
2015-08-30  4:21       ` Рысь
2015-08-30  4:46         ` Rich Felker [this message]
2015-08-30  5:13           ` Рысь
2015-08-30  5:30             ` Rich Felker
2015-08-30  9:00               ` Szabolcs Nagy
2015-08-30 17:09                 ` Rich Felker
2015-08-30 17:45                   ` u-wsnj
2015-08-30 17:13               ` Рысь
2015-08-30 17:38                 ` Rich Felker
2015-08-30  5:18 ` Рысь
2015-08-30  5:31   ` Rich Felker
2015-08-30 17:21     ` Рысь
2015-08-30 19:29       ` Message localization [Was: Re: [musl] Adjustments to roadmap] Rich Felker
2015-09-01  4:26         ` Рысь
2015-09-01  4:47           ` Rich Felker
2015-09-02  2:26             ` Рысь
2015-09-02  2:28               ` Rich Felker
2015-09-07 13:51                 ` Рысь
2015-09-08 15:18                   ` Rich Felker
2015-08-31  7:09 ` Adjustments to roadmap 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=20150830044654.GJ7833@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).