From: Adrian Bunk <bunk@stusta.de>
To: akuster808 <akuster808@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: musl thoughts
Date: Fri, 22 Mar 2019 21:35:22 +0200 [thread overview]
Message-ID: <20190322193522.GA14099@localhost> (raw)
In-Reply-To: <4ac23adb-9be1-c09b-7794-54c2dbd04a24@gmail.com>
On Fri, Mar 22, 2019 at 07:53:03AM -0700, akuster808 wrote:
> On 3/21/19 6:11 PM, Andreas Müller wrote:
>...
> > As you might guess I'd prefer 3 because:
> > + Many patches can go and don't need maintenance on upstream refactoring anymore
> > + Burden for people sending patches would be reduced
> > + Recipes not building with musl currently might work without further
> > modification
> > + Just in case musl stops (we have seen this before with others e.g
> > ulibc) the cleanup would be reduced
>
> Didn't we do something like this with glibc? We carried several patches
> that where rejected and just recently got removed so there is a
> precedent for carrying OE specific changes so it seems like a
> reasonable approach.
The glibc patches that got removed were patches where it can be
questioned whether they should have ever been applied.
glibc still carries far too many patches that simply shouldn't be there.
All this is different from the musl situation where some kind of
patching is required somewhere at least short-term.
> - armin
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
next prev parent reply other threads:[~2019-03-22 19:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-22 1:11 musl thoughts Andreas Müller
2019-03-22 14:53 ` akuster808
2019-03-22 19:35 ` Adrian Bunk [this message]
2019-03-22 20:03 ` Adrian Bunk
2019-03-22 22:20 ` Khem Raj
2019-03-23 17:30 ` Adrian Bunk
2019-03-22 22:18 ` Khem Raj
2019-03-23 21:16 ` Adrian Bunk
2019-03-23 21:22 ` Andreas Müller
2019-03-23 21:53 ` Adrian Bunk
2019-03-23 22:00 ` Andreas Müller
2019-03-25 15:36 ` Andrea Adami
2019-03-25 16:10 ` Adrian Bunk
2019-03-25 16:26 ` Andreas Müller
2019-03-25 17:15 ` Andreas Müller
2019-03-25 17:36 ` Andreas Müller
2019-03-25 18:03 ` Adrian Bunk
2019-03-25 19:46 ` Andreas Müller
2019-03-25 17:46 ` Adrian Bunk
2019-03-25 21:11 ` Andreas Müller
2019-03-25 22:38 ` Khem Raj
2019-03-25 16:31 ` Andrea Adami
2019-03-25 17:07 ` Adrian Bunk
2019-03-25 17:44 ` Khem Raj
2019-03-25 18:23 ` Adrian Bunk
2019-03-25 15:46 ` Mark Hatle
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190322193522.GA14099@localhost \
--to=bunk@stusta.de \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.