[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMKF1sq+qbSPSOaU4iyi1Vr8=Xvzuyd2gHx2QN5PPNtUo0JLAQ@mail.gmail.com>
Date: Mon, 18 Aug 2014 12:14:08 -0700
From: Khem Raj <raj.khem@...il.com>
To: Paul Barker <paul@...lbarker.me.uk>
Cc: Patches and discussions about the oe-core layer <openembedded-core@...ts.openembedded.org>,
openembeded-devel <Openembedded-devel@...ts.openembedded.org>,
"yocto@...toproject.org" <yocto@...toproject.org>, musl@...ts.openwall.com
Subject: Re: [OE-core] Announcing meta-musl OE/Yocto layer supporting musl C library
On Mon, Aug 18, 2014 at 12:08 PM, Paul Barker <paul@...lbarker.me.uk> wrote:
>> That would be handy too. But I wanted was to keep this info in project
>> for folks to try it out.
>>
>
> I'll just post one ticket for now.
>
Thats fine too.
> I think I've got a fix for e2fsprogs as well.
Great. when we write patches that arise out of musl systems we should
make sure that
1. If patch fixes a genuine issue surfaced with musl, fight it out ar
respective package upstream and in OE universe add it to the original
layer where recipe primarily resides
but we can keep the patches in meta-musl as a last resort.
2. If its something musl specific then lets keep it in meta-musl and
see how musl can be changed to fix it.
Thanks
-Khem
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
