From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx-3.enea.com (sestofw01.enea.se [192.36.1.252]) by yocto-www.yoctoproject.org (Postfix) with SMTP id 4B80BE00CE1 for ; Fri, 11 Apr 2014 00:03:04 -0700 (PDT) Received: from localhost.enea.se (192.168.14.171) by smtp.enea.com (172.21.1.208) with Microsoft SMTP Server id 14.3.158.1; Fri, 11 Apr 2014 09:02:58 +0200 Message-ID: <534793A2.2000603@enea.com> Date: Fri, 11 Apr 2014 10:02:58 +0300 From: Vali Cobelea Organization: ENEA User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Diego Sueiro References: <534416F0.10109@enea.com> <9507315.eLP4En45Q5@peggleto-mobl5.ger.corp.intel.com> <53452733.2070806@enea.com> <33266524.grSQoK8z6t@peggleto-mobl5.ger.corp.intel.com> <53452985.7020202@enea.com> In-Reply-To: X-Originating-IP: [192.168.14.171] Cc: yocto@yoctoproject.org, Alexandru Vaduva , Paul Eggleton Subject: Re: CGL compliance layer initiative X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2014 07:03:07 -0000 Content-Type: multipart/alternative; boundary="------------040708040705000806020904" --------------040708040705000806020904 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Hi Diego, Thank you for your interest in the meta-cgl layer. Please be aware that the layer is in its alpha state, as I said an initiative that started with a layer. The branch is 'master', no custom things yet. Below you can find the instructions to clone all of the "dependency layers": git clonegit://git.yoctoproject.org/meta-qt3 git clonegit://git.yoctoproject.org/meta-virtualization git clonegit://git.yoctoproject.org/meta-selinux git clonegit://git.yoctoproject.org/meta-cloud-services git clonegit://git.yoctoproject.org/meta-security git clonehttps://github.com/joaohf/meta-openclovis.git Also, since there are duplicated recipes in these layers, please add the following BBMASK in cong/local.conf (big thank you to Alex Vaduva for this): BBMASK = "meta-cloud-services/meta-openstack/recipes-support/lvm2|meta-security/recipes-security/libcap-ng" Let me know how the test goes Deigo. Best regards, Vali On 04/11/2014 12:35 AM, Diego Sueiro wrote: > > Vali, > > I'm excited to see CGL support for Yocto. > I'm going to test this layer as soon as possible. > > One question, which branch of Yocto is it based on? > > Regards, > > -- > *dS > Diego Sueiro > sent from mobile. > > On Apr 9, 2014 11:05 AM, "Vali Cobelea" > wrote: > > OK Paul, that indeed makes sense, I really did not knew that > preliminary versions of layers are accepted. > I will discuss around here and if everything goes OK we will start > the move in the "public" layer index. > I also do agree with an all-together strategy, no matter for the > layer state. > > > Much appreciated, > Vali > > > On 04/09/2014 02:01 PM, Paul Eggleton wrote: > > On Wednesday 09 April 2014 13:55:47 Vali Cobelea wrote: > > On 04/09/2014 01:51 PM, Paul Eggleton wrote: > > On Tuesday 08 April 2014 18:34:08 Vali Cobelea wrote: > > Here at ENEA we decided to take the initiative > regarding the CGL > compliance when it comes to the Yocto Project. > For this we started the work on a dedicated layer > called 'meta-cgl' > > which can be accessed / cloned from here: > http://git.enea.com/git/?p=linux/meta-cgl.git > git clone git@git.enea.com:linux/meta-cgl > > Have a look of the things we got there so far, > please remember that > there is still plenty of work to be done (layer > architecture, CGL > requirements coverage mode and so on). > It is a little bit more than a stub layer, > consider it a starting point > for the direction we would like to have with this > layer. > > Any input is much appreciated, lets keep the > discussion by this email > thread and see where it goes. > > I don't have anything to offer on the layer contents, > but I would say in > order to make it easy for people to find this layer I > would strongly > encourage you to> > submit it to the OpenEmbedded layer index: > http://layers.openembedded.org/layerindex/submit/ > > Thank you for the input. > We will keep the layer for a short period of time at the > current > location while getting other ideas regarding the content / > architecture. > The layer initiative will also be raised up in the board > advisory > meeting, in order to get even more input. > After which we will make it easier to find, access and use > for anyone, > exactly as you suggested. > > OK, as the maintainer it's totally up to you. > > I would say though generally that I'd like to see more people > adding their > work-in-progress layers to the layer index, even if at some > time later they > will be moved elsewhere or absorbed into another layer - it > just makes it > easier to point people to the layer index so they can find > recipes that have > already been written, rather than having to re-write them from > scratch. > > Cheers, > Paul > > > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto > --------------040708040705000806020904 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit
Hi Diego,

Thank you for your interest in the meta-cgl layer.
Please be aware that the layer is in its alpha state, as I said an initiative that started with a layer.

The branch is 'master', no custom things yet.
Below you can find the instructions to clone all of the "dependency layers":

git clone git://git.yoctoproject.org/meta-qt3 
git clone git://git.yoctoproject.org/meta-virtualization 
git clone git://git.yoctoproject.org/meta-selinux 
git clone git://git.yoctoproject.org/meta-cloud-services 
git clone git://git.yoctoproject.org/meta-security 
git clone https://github.com/joaohf/meta-openclovis.git

Also, since there are duplicated recipes in these layers, please add the following BBMASK in cong/local.conf  (big thank you to Alex Vaduva for this):

BBMASK = "meta-cloud-services/meta-openstack/recipes-support/lvm2|meta-security/recipes-security/libcap-ng"


Let me know how the test goes Deigo.


Best regards,
Vali

On 04/11/2014 12:35 AM, Diego Sueiro wrote:

Vali,

I'm excited to see CGL support for Yocto.
I'm going to test this layer as soon as possible.

One question, which branch of Yocto is it based on?

Regards,

--
*dS
Diego Sueiro
sent from mobile.

On Apr 9, 2014 11:05 AM, "Vali Cobelea" <valentin.cobelea@enea.com> wrote:
OK Paul, that indeed makes sense, I really did not knew that preliminary versions of layers are accepted.
I will discuss around here and if everything goes OK we will start the move in the "public" layer index.
I also do agree with an all-together strategy, no matter for the layer state.


Much appreciated,
Vali


On 04/09/2014 02:01 PM, Paul Eggleton wrote:
On Wednesday 09 April 2014 13:55:47 Vali Cobelea wrote:
On 04/09/2014 01:51 PM, Paul Eggleton wrote:
On Tuesday 08 April 2014 18:34:08 Vali Cobelea wrote:
Here at ENEA we decided to take the initiative regarding the CGL
compliance when it comes to the Yocto Project.
For this we started the work on a dedicated layer called 'meta-cgl'

which can be accessed / cloned from here:
    http://git.enea.com/git/?p=linux/meta-cgl.git
    git clone git@git.enea.com:linux/meta-cgl

Have a look of the things we got there so far, please remember that
there is still plenty of work to be done (layer architecture, CGL
requirements coverage mode and so on).
It is a little bit more than a stub layer, consider it a starting point
for the direction we would like to have with this layer.

Any input is much appreciated, lets keep the discussion by this email
thread and see where it goes.
I don't have anything to offer on the layer contents, but I would say in
order to make it easy for people to find this layer I would strongly
encourage you to>
submit it to the OpenEmbedded layer index:
    http://layers.openembedded.org/layerindex/submit/
Thank you for the input.
We will keep the layer for a short period of time at the current
location while getting other ideas regarding the content / architecture.
The layer initiative will also be raised up in the board advisory
meeting, in order to get even more input.
After which we will make it easier to find, access and use for anyone,
exactly as you suggested.
OK, as the maintainer it's totally up to you.

I would say though generally that I'd like to see more people adding their
work-in-progress layers to the layer index, even if at some time later they
will be moved elsewhere or absorbed into another layer - it just makes it
easier to point people to the layer index so they can find recipes that have
already been written, rather than having to re-write them from scratch.

Cheers,
Paul


--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

--------------040708040705000806020904--