[yocto] CGL compliance layer initiative

Bruce Ashfield bruce.ashfield at windriver.com
Fri Apr 11 05:45:53 PDT 2014


On 14-04-11 03:02 AM, Vali Cobelea wrote:
> 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
> <http://twiki.enea.se/twiki/bin/edit/Git://git/yoctoproject/org/Meta-qt3?topicparent=EETeng.EneaLinuxCGLBuildInstructions;nowysiwyg=0>
> git clonegit://git.yoctoproject.org/meta-virtualization
> <http://twiki.enea.se/twiki/bin/edit/Git://git/yoctoproject/org/Meta-virtualization?topicparent=EETeng.EneaLinuxCGLBuildInstructions;nowysiwyg=0>
> git clonegit://git.yoctoproject.org/meta-selinux
> <http://twiki.enea.se/twiki/bin/edit/Git://git/yoctoproject/org/Meta-selinux?topicparent=EETeng.EneaLinuxCGLBuildInstructions;nowysiwyg=0>
> git clonegit://git.yoctoproject.org/meta-cloud-services
> <http://twiki.enea.se/twiki/bin/edit/Git://git/yoctoproject/org/Meta-cloud-services?topicparent=EETeng.EneaLinuxCGLBuildInstructions;nowysiwyg=0>
> git clonegit://git.yoctoproject.org/meta-security
> <http://twiki.enea.se/twiki/bin/edit/Git://git/yoctoproject/org/Meta-security?topicparent=EETeng.EneaLinuxCGLBuildInstructions;nowysiwyg=0>
> 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"
>

What exactly are you finding with lvm2 in meta-cloud-services ?

Bruce

>
> 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 at enea.com
>> <mailto:valentin.cobelea at 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 at 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 at yoctoproject.org <mailto:yocto at yoctoproject.org>
>>     https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
>




More information about the yocto mailing list