From: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
To: Trevor Woerner <twoerner@gmail.com>
Cc: Lists Linaro-dev <linaro-dev@lists.linaro.org>,
Patches and discussions about the oe-core layer
<Openembedded-core@lists.openembedded.org>
Subject: Re: Changes in Linaro layers for OpenEmbedded
Date: Thu, 09 May 2013 23:25:40 +0200 [thread overview]
Message-ID: <518C1454.4030701@linaro.org> (raw)
In-Reply-To: <CAHUNapTEOfwR9OATGGKOtrpHWwisVh0xXm5P2jKUgEitznpxNw@mail.gmail.com>
W dniu 09.05.2013 20:42, Trevor Woerner pisze:
> On Thu, May 9, 2013 at 12:57 PM, Marcin Juszkiewicz
> <marcin.juszkiewicz@linaro.org> wrote:
>> Who will maintain those layers after my leave? This was not decided
>> yet. There are few guys at Linaro who know how to use OpenEmbedded
>> but most of them is outside of Builds and Baselines team.
> To me this implies that these layers and this effort of yours isn't
> part of any "official" Linaro build process/procedure. Would this
> assumption be correct?
No.
First Linaro layer for OpenEmbedded was created by Ken Werner from
Toolchain Working Group as they considered OE as a test tool. Then
AArch64 bootstrap was needed so I stepped in and took maintenance of it
(Ken was not at Linaro at that time), added meta-aarch64, cleaned up etc.
Those layers are used as part of official Linaro build process. All
AArch64 rootfs images are built using OpenEmbedded. Note that this
excludes kernels which (for some reasons) were cross built as Ubuntu
packages.
At Linaro we have many teams and some of them are using OpenEmbedded or
will do it soon. One of reasons is lack of ARM big-endian distributions
on a market.
Look at numbers from "git shortlog":
Marcin Juszkiewicz (341):
Ken Werner (28):
Riku Voipio (17):
Khem Raj (7):
Ricardo Salveti de Araujo (5):
Fathi Boudra (2):
Ken is not at Linaro, Khem never was and those commits are fixes from
him, Ricardo is back at Canonical. Riku has OE knowledge but also lot of
other duties.
And so far only OpenSUSE has packages for AArch64 mass built while all
Linaro tools were made for Ubuntu repositories...
next prev parent reply other threads:[~2013-05-09 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-09 16:57 Changes in Linaro layers for OpenEmbedded Marcin Juszkiewicz
2013-05-09 18:42 ` Trevor Woerner
2013-05-09 21:25 ` Marcin Juszkiewicz [this message]
[not found] ` <CAGNsrLBckfhAKwGVsyCm3KArBU=-CMiMd55s-iL+XatU0x9gQg@mail.gmail.com>
2013-05-10 12:37 ` Tom Gall
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=518C1454.4030701@linaro.org \
--to=marcin.juszkiewicz@linaro.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=linaro-dev@lists.linaro.org \
--cc=twoerner@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox