mailing list of musl libc
 help / color / mirror / code / Atom feed
From: u-wsnj@aetey.se
To: musl@lists.openwall.com
Subject: Re: Adjustments to roadmap
Date: Sun, 30 Aug 2015 19:45:18 +0200	[thread overview]
Message-ID: <20150830174518.GH11263@example.net> (raw)
In-Reply-To: <20150830170932.GN7833@brightrain.aerifal.cx>

On Sun, Aug 30, 2015 at 01:09:32PM -0400, Rich Felker wrote:
> On Sun, Aug 30, 2015 at 11:00:13AM +0200, Szabolcs Nagy wrote:

> > there are other reasons for symvers: debian is willing to
> > accept patches for a musl based debian, however they use
> > symbol versioning a lot to avoid frequently changing the .so
> > name.  i.e. if we support symvers we may be able to create
> > a musl based debian package repo without much effort or
> > maintainance work. (it is probably possible to rebuild all
> > dependent packages on every minor abi change in a library,
> > but then somebody would need to do that work and users will
> > need to download more packages on an update).

It would be interesting to have some idea about the frequency of
the cases when libraries break the ABIs and the number/percentage of
the packages which would need rebuilding because of this.

> This seems like an area where there would be concrete benefit. Any
> word from ppl interested in Debian/musl?

Indeed it would be interesting to hear from Debian.
Such a port would be of course a nice testbed and showcase for musl.

If despite the expectations this could be done without symbol versioning,
then it would also serve as an indication of the importance of the
versioning or lack thereof.

> Being that the only significant feedback on symbol versioning so far
> has been negative, I lean towards holding off on prioritizing this
> issue while we wait for more opinions or compelling reasons to support

+1
(the less developer time is consumed before the need is proven, the better)

Rune



  reply	other threads:[~2015-08-30 17:45 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
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 [this message]
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=20150830174518.GH11263@example.net \
    --to=u-wsnj@aetey.se \
    --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).