On 04/16/2018 07:05 PM, Andreas Müller wrote:
Hi,
I am not happy plastering patches around for musl. This gets even
worse when I see patches like this [1]: Just wipe away security checks
unconditionally - the developers did introduce this check not just for
fun I guess...
I have seen this already elsewhere so: musl maintainers please take
care not to modify code for glibc!
[1]
https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-core/systemd/systemd/0001-Use-getenv-when-secure-versions-are-not-available.patch
Andreas
Hi Anreas,
I can see I rebased this patch. So I think I need to reply.
I agree with you that musl related patches should not affect glibc.
How about we using something like SRC_URI_append_libc-musl to organize
the musl related patches?
Or do you have some other suggestion?
Best Regards,
Chen Qi
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
