From: Tomasz Duda <email@example.com>
To: Rich Felker <firstname.lastname@example.org>
Cc: Florian Weimer <email@example.com>, firstname.lastname@example.org
Subject: Re: [musl] AF_LOCAL
Date: Mon, 11 Jul 2022 21:53:20 +0200 [thread overview]
Message-ID: <CANs4VLyEaBsCaDE3cGzanWNZQs2LadWtqYzeSMFbwMcDyjo99w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1368 bytes --]
I love alpine since it is small distribution which have a lot of packages.
The problem is that I ended up patching libc during building docker image.
I guess that I'm not only one who meet this problem. For most users it
would be deal breaker.
pon., 11 lip 2022 o 17:22 Rich Felker <email@example.com> napisał(a):
> On Mon, Jul 11, 2022 at 05:04:15PM +0900, Tomasz Duda wrote:
> > Done is better than perfect. It prevents some applications from starting
> > it is pretty bad.
> No, inconsistent is worse than not at all. Not-at-all forces
> applications to fix the wrong assumption. Inconsistent means
> applications compile and run but silently (in sense of not producing
> an error at build and/or run time) do the wrong thing on some systems.
> One of the main criteria for exclusion of an extension from musl is
> the existence of multiple conflicting historical definitions for the
> same extension.
> > On Mon, Jul 11, 2022, 16:56 Florian Weimer <firstname.lastname@example.org> wrote:
> > > * Tomasz Duda:
> > >
> > > > It seems to be implemented in other libs.
> > >
> > > Yes, but not in a consistent fashion.
> > >
> > > Thanks,
> > > Florian
> > >
> > >
[-- Attachment #2: Type: text/html, Size: 2069 bytes --]
prev parent reply other threads:[~2022-07-11 19:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 14:32 Tomasz Duda
2022-07-10 18:06 ` Markus Wichmann
2022-07-11 4:48 ` Florian Weimer
2022-07-11 7:54 ` Tomasz Duda
2022-07-11 7:56 ` Florian Weimer
2022-07-11 8:04 ` Tomasz Duda
2022-07-11 15:22 ` Rich Felker
2022-07-11 19:53 ` Tomasz Duda [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).