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.
https://github.com/pikvm/kvmd/pull/101/commits/5698bf29d5948e79bffd9a7bebeec77e39d8f18f#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557



pon., 11 lip 2022 o 17:22 Rich Felker <dalias@libc.org> 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 so
> 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 <fweimer@redhat.com> wrote:
>
> > * Tomasz Duda:
> >
> > > It seems to be implemented in other libs.
> >
> > Yes, but not in a consistent fashion.
> >
> > Thanks,
> > Florian
> >
> >