From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-core@lists.openembedded.org
Cc: poky@yoctoproject.org, openembedded-devel@lists.openembedded.org
Subject: Re: Piglit in Poky
Date: Tue, 24 Dec 2013 15:22:32 +0100 [thread overview]
Message-ID: <l9c5ar$2mb$1@ger.gmane.org> (raw)
In-Reply-To: <CAJTo0LZsBfxGm=OJPa++egDjL6L0ZABMebTtTr_Bmw_TdQrohg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Burton, Ross schreef op 23-12-13 19:01:
> Hi,
>
> We'd like to integrate Piglit (an OpenGL test suite) into Poky so that we
> can run automated QA on the GL stack. Piglit is currently residing in
> meta-oe, but as Poky is a self-contained project we can't just add
> meta-oe to it: apart from the size of meta-oe, we can't ensure stability
> if meta-oe makes incompatible changes that affect Poky.
>
> Piglit isn't a stand-alone package, there are the dependencies of waffle,
> python-mako and python-numpy to consider too. There are two
> possibilities I can see:
>
> 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?
>
> 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.
Speaking of layers, can you *please* rename meta-yocto to meta-poky? It's
what it's actually is and would remove a lot of confusion when trying to
explain that yocto is not a distro, even if the distro layer is called
'meta-yocto'.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFSuZioMkyGM64RGpERAgglAKCHbnivOF3g/ZVMGYadm4pDDzfKVQCdGqlY
YdzFCCkRyP8WWMuNJRlR6x4=
=4M6P
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-12-24 14:22 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 ` [poky] " Martin Jansa
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 [this message]
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='l9c5ar$2mb$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=poky@yoctoproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox