From: "João Henrique Ferreira de Freitas" <joaohf@gmail.com>
To: Vali Cobelea <valentin.cobelea@enea.com>,
Yocto list discussion <yocto@yoctoproject.org>
Cc: Alexandru Vaduva <Alexandru.Vaduva@enea.com>
Subject: Re: CGL compliance layer initiative
Date: Thu, 10 Apr 2014 23:20:27 -0300 [thread overview]
Message-ID: <5347516B.2020601@gmail.com> (raw)
In-Reply-To: <534416F0.10109@enea.com>
Hi Vali,
I took a look into meta-cgl and I've builded with all master (lots of
warning) layers described in README file. Good initiative.
I noted that in README file you mention about 'meta-openclovis'. I
believed that you got openipmi recipe from meta-openclovis, because
meta-cgl has a .bbappend to it. Am I right?
Indeed meta-openclovis has three recipes that could stay in meta-cgl:
openhpi, openhpi-subagent and openipmi.
What about the quality of recipes that meta-cgl will use from others
layers? For instance the patchs/stable code release/features in net-snmp
recipe
is aligned with CGL requirements? My concern is about the scope and
stability of meta-cgl.
Thanks.
PS:
Build Configuration:
BB_VERSION = "1.23.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-13.10"
TARGET_SYS = "i586-poky-linux"
MACHINE = "qemux86"
DISTRO = "poky"
DISTRO_VERSION = "1.6+snapshot-20140411"
TUNE_FEATURES = "m32 i586"
TARGET_FPU = ""
meta = "master:863cc7483f5ee43189537940de8ee5c0964d24cc"
meta-cgl = "master:63a890e8513ff50279a1ce53e45a0394fd05b2b6"
meta-qt3 = "master:3016129d90b7ac8517a5227d819f10ad417b5b45"
meta-networking
meta-filesystems
meta-oe
meta-perl = "master:477ccd867cc71f8277f2670b7be34b3b15300052"
meta-yocto
meta-yocto-bsp = "master:863cc7483f5ee43189537940de8ee5c0964d24cc"
meta-virtualization = "master:7544bfb6ec7efd283e7e7ff712e91452fdffb534"
meta-openclovis = "master:68f9a9c4ab01590d63506126660e3316ba668f99"
meta-selinux = "master:0362287928bc0a58b755488ebd74441c28eeeee2"
meta-security = "master:7e8c7918d9ff8fc89579502cc136e37deecdfd96"
meta-openstack = "master:940e7d24c418a9cbb93850c31d00e4f1edeaf764"
--
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
next prev parent reply other threads:[~2014-04-11 2:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 15:34 CGL compliance layer initiative Vali Cobelea
2014-04-08 15:38 ` Chris Larson
2014-04-08 15:41 ` Vali Cobelea
2014-04-08 15:46 ` Chris Larson
2014-04-08 15:49 ` Chris Larson
2014-04-09 6:45 ` Vali Cobelea
2014-04-09 10:51 ` Paul Eggleton
2014-04-09 10:55 ` Vali Cobelea
2014-04-09 11:01 ` Paul Eggleton
2014-04-09 11:05 ` Vali Cobelea
2014-04-10 21:35 ` Diego Sueiro
2014-04-11 7:02 ` Vali Cobelea
2014-04-11 12:45 ` Bruce Ashfield
2014-04-11 13:38 ` Alexandru Vaduva
2014-04-11 2:20 ` João Henrique Ferreira de Freitas [this message]
2014-04-11 7:10 ` Vali Cobelea
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=5347516B.2020601@gmail.com \
--to=joaohf@gmail.com \
--cc=Alexandru.Vaduva@enea.com \
--cc=valentin.cobelea@enea.com \
--cc=yocto@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 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.