From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Poky Project <poky@yoctoproject.org>,
OE-devel <openembedded-devel@lists.openembedded.org>,
OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [poky] Piglit in Poky
Date: Wed, 8 Jan 2014 17:27:53 +0100 [thread overview]
Message-ID: <20140108162753.GZ3709@jama> (raw)
In-Reply-To: <CAJTo0LaEgLWZHk34e-_-+z69Zw3J+S1zGFFJAONjfYBDQ1TehQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2470 bytes --]
On Wed, Jan 08, 2014 at 04:09:10PM +0000, Burton, Ross wrote:
> Hi,
>
> Despite a good start this thread got rapidly hijacked, so let's try again!
>
> On 24 December 2013 01:09, Philip Balister <philip@balister.org> wrote:
> >> 1) Move piglit and deps to oe-core. Piglit is for QA purposes only
> >> and pushes the boundaries of "core platform". In a sense this is a
> >> repeat of the discussion we had with Midori... does oe-core contain
> >> everything needed to sufficiently exercise the core components it
> >> ships or not?
> >
> > I expect Richard will push back on this, and I would support him here.
>
> Probably best to let Richard speak for himself here. :)
>
> >> 2) Add piglit and deps to meta-yocto. Probably a new layer called
> >> meta-yocto-qa (or similar) because the Yocto Compatible guidelines
> >> forbid mixing distribution policy and recipes. We'd need to sync
> >> meta-yocto-qa with the pieces of meta-oe that we want somehow, but
> >> that's our problem.
> >
> > So meta-yocto is right out. I'm a user of numpy, and I certainly do not
> > want to include something called meta-yocto-qa just to pick up numpy.
>
> Right, so my point with the syncing was that this meta-yocto-qa layer
> would be a copy of recipes from other places through combo-layer, and
> would be clearly marked as such.
>
> Reviewing the options:
>
> 1) Add python-mako, python-numpy, waffle and piglit to oe-core, for
> all BSPs to use.
> 2) Add python-mako, python-numpy, waffle and piglit to meta-yocto
> (effectively read-only clones with combo-layer, maintained in meta-oe
> still) for Poky to use.
> 3) Add meta-python layer to Poky, and waffle/piglit to meta-yocto
> (read-only clones) for Poky to use.
4) meta-python in meta-oe (at least for easier copy somewhere else with combo-layer)
>
> Paul raises a good point about other BSPs potentially using Piglit to
> test their GL stacks. Do any other BSPs test their GL integration,
> and if so what tooling to they use? I'm only pushing for Piglit
> because it's what the Intel driver team use to test Mesa, but if
> nobody else wants to use it then that's an argument for keeping it in
> Poky (or even cloning it into meta-intel?).
>
> Ross
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2014-01-08 16:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 18:01 Piglit in Poky Burton, Ross
2013-12-24 1:09 ` Philip Balister
2013-12-24 10:50 ` [oe] " Martin Jansa
2014-01-06 11:22 ` Paul Eggleton
2013-12-28 11:41 ` Paul Eggleton
2014-01-08 16:09 ` Burton, Ross
2014-01-08 16:27 ` Martin Jansa [this message]
2014-01-08 17:01 ` Richard Purdie
2014-01-08 17:14 ` Nicolas Dechesne
2014-01-08 18:44 ` Philip Balister
2014-01-08 19:46 ` Burton, Ross
2014-01-08 21:14 ` [oe] " Otavio Salvador
2013-12-24 14:22 ` Koen Kooi
2013-12-28 11:48 ` Paul Eggleton
2013-12-28 15:28 ` Koen Kooi
2013-12-28 22:33 ` Philip Balister
2013-12-29 15:44 ` Koen Kooi
2014-01-03 11:25 ` Andrei Gherzan
2014-01-03 13:26 ` [oe] " Paul Eggleton
2014-01-03 13:37 ` Martin Jansa
2014-01-03 13:50 ` Paul Eggleton
2014-01-03 15:06 ` Andrei Gherzan
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=20140108162753.GZ3709@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=poky@yoctoproject.org \
--cc=ross.burton@intel.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