<div><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 14, 2019 at 4:44 AM Richard Purdie <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, 2019-06-14 at 10:29 +0300, Adrian Bunk wrote:<br>
> This removes clearly incorrect musl patches and marks<br>
> systemd as incompatible with musl until these issues<br>
> are fixed.<br>
> <br>
> The previous status quo where systemd was made compiling<br>
> with patches that are known to introduce bugs and security<br>
> vulnerabilities silently delivered a sub-standard package<br>
> to users, this change makes it clear where work is needed<br>
> to be done by people interested in systemd on musl.<br>
> <br>
> Patches that are merely questionable or not upstreamable<br>
> are not touched.<br>
<br>
I'll be interested to see what others think of this, I can't imagine<br>
this move being very popular...<br>
</blockquote><div dir="auto"><br></div><div dir="auto">There are real products using this combination</div><div dir="auto">And this is not a good message, eventually we want to either fix or stop supporting this but I think now is not the time </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
You can make arguments both ways.<br>
<br>
Cheers,<br>
<br>
Richard<br>
<br>
-- <br>
_______________________________________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openembedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/mailman/listinfo/openembedded-core</a><br>
</blockquote></div></div>