From: Ariadne Conill <ariadne@dereferenced.org>
To: Rich Felker <dalias@libc.org>, musl@lists.openwall.com
Cc: musl@lists.openwall.com, ell1e <kittens@wobble.ninja>
Subject: Re: [musl] Would it to be possible to get strtoll_l?
Date: Wed, 07 Oct 2020 09:41:37 -0600 [thread overview]
Message-ID: <2107314.7dBsPmfxI7@localhost> (raw)
In-Reply-To: <c127ba0d-ced6-a248-7484-6a5e378b102b@wobble.ninja>
Hello,
On Wednesday, October 7, 2020 7:44:11 AM MDT ell1e wrote:
[...]
> But then again, most of these things can be worked around when porting
> to musl. But how many people will bother, and how many programs be left
> behind as a result and not work on Alpine etc.? Is that some quantity
> that will bother anyone?
Alpine is in an atypical position of both being a distribution and an overall
platform, which just happens to use musl as one of its components. We extend
musl with other libraries that implement functionality considered out of scope
for musl; the strtoll_l() and related functions could be provided in this way.
Other examples of such extensions include libucontext, musl-obstack, etc.
I don't think that all situations require musl to provide functionality in
order to solve the problem -- in fact, in general, I think that the amount of
situations where that is actually required is minimal. I would rather musl
focus on providing a high quality core libc implementation instead of
implementing things that they don't want to implement and can be provided
elsewhere.
At any rate, the point here being that simply because musl does not implement
something does not mean it cannot be implemented in Alpine at large -- and
yes, this means that sometimes programs built on Alpine require the other
runtime components (like libucontext or musl-obstack or whatever) along side
musl. I don't consider that a problem, since those components are readily
available for any other distribution to ship if they wish to.
Ariadne
next prev parent reply other threads:[~2020-10-07 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 0:34 ell1e
2020-10-01 2:35 ` Rich Felker
2020-10-01 4:36 ` ell1e
2020-10-01 5:24 ` Ellie
2020-10-01 8:08 ` Ellie
2020-10-01 15:47 ` Rich Felker
2020-10-07 13:44 ` ell1e
2020-10-07 13:52 ` Ellie
2020-10-07 14:58 ` 罗勇刚(Yonggang Luo)
2020-10-07 15:41 ` Ariadne Conill [this message]
2020-10-07 19:37 ` 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=2107314.7dBsPmfxI7@localhost \
--to=ariadne@dereferenced.org \
--cc=dalias@libc.org \
--cc=kittens@wobble.ninja \
--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).