[OE-core] Should systemd be marked as incompatible with musl?
Adrian Bunk
bunk at stusta.de
Wed May 29 07:31:01 UTC 2019
On Tue, May 28, 2019 at 04:10:45PM -0700, Andre McCurdy wrote:
> On Sat, May 25, 2019 at 12:25 AM Adrian Bunk <bunk at stusta.de> wrote:
>...
> > Supporting musl is a real pain across the board,
> > with new issues all the time.
>
> There are always new issues and bugs to be solved in OE as a
> consequence of trying to keep all packages up to date. Whether the
> issues arising from musl are a real pain or a fun new set of problems
> to solve is mostly a matter of perspective.
Usually someone submits a change, and later gets notified that the
change was dropped from master-next due to a musl issue.
That's not fun.
And all these compile errors with musl due to header order are a real WTF,
every other library (not limited to C libraries) is now doing headers
properly so that any order works. No fun in supporting a broken design.
> > For really tiny systems you need both a tiny C library and a tiny init> system, so not properly supporting the combination of both forces users
> > to use alternative options instead of OE.
> >
> > Which minimizes the benefits gained by the pains of supporting musl.
>
> A modern tiny init system would be nice to have, but it's not
> essential or fair to say that musl is useless without one. Many
> projects, especially tiny ones, manage fine with init scripts and
> custom process management.
I was not asking for "modern".
If init scripts are not default and CI tested with musl,
then init scripts will soon become a broken part of OE.
>...
> A few pragmatic patches applied by OE would go a long way to bridging
> the conflicting goals of the two upstream projects. It's basically the
> approach we've taken already - the question is just one of improving
> the patches we already have (and maybe patching musl to add missing
> functionality instead of only trying to patch systemd to not depend on
> it).
I already tried patching musl in OE.
The change got reverted.
There are people who think that OE-specific patches to musl are not
acceptable, and that it is better to force everyone in OE to patch
individual packages all the time instead of adding a not upstreamable
patch to musl.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
More information about the Openembedded-core
mailing list