Skip to contentSkip to conversation

CGL compliance layer initiative

DISCUSSION Vali Cobelea 7 participants 16 messages Apr 8, 2014 – Apr 11, 2014

lore
Share & tools
lore
#0 lore raw

Hi,

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 [email protected]: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.

Best regards,
Vali

#1 lore raw
Quoted 8 lines · Vali Cobelea

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 [email protected]:linux/meta-cgl

Quoted 9 lines

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.

Is there no anonymous clone url, or are you giving us your ssh keys? ;)

Signature · 5 lines
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
#2 lore raw

Hi,

It should work as I tried it outside the company network; otherwise I'll ping back the IT guys to allow anonymous access.

Sorry for any inconvenience,
Vali

Quoted 28 lines · Chris Larson

On Tue, Apr 8, 2014 at 8:34 AM, Vali Cobelea <[email protected] <mailto:[email protected]>> 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 [email protected]: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.

Is there no anonymous clone url, or are you giving us your ssh keys? ;)

Signature · 5 lines
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
#3 lore raw
Quoted 3 lines · Vali Cobelea

It should work as I tried it outside the company network; otherwise I'll ping back the IT guys to allow anonymous access.

You tried it, yes, but you have the ssh keys necessary to authenticate as the git user on that server, which no one outside your company does :) If you want folks to be able to clone your repository without having to add their public keys to your ssh server config, then you will indeed want to contact IT to get anonymous access going.

Signature · 5 lines
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
#4 lore raw
In reply to Vali Cobelea
Quoted 8 lines · Vali Cobelea

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 [email protected]:linux/meta-cgl

git clone git://git.enea.com/linux/meta-cgl.git for those of us who don't work for ENEA, works fine :)

Signature · 5 lines
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
#5 lore raw

Hi Chris,

I do know that I got the right ssh keys, and also I do know that changing the 'git@' to 'git://' always works for any git repo, well all git users should do :-)

Again much appreciated for the interest in our layer.

Best regards,
Vali

Quoted 19 lines · Chris Larson

On Tue, Apr 8, 2014 at 8:34 AM, Vali Cobelea <[email protected] <mailto:[email protected]>> 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 [email protected]:linux/meta-cgl

git clone git://git.enea.com/linux/meta-cgl.git <http://git.enea.com/linux/meta-cgl.git> for those of us who don't work for ENEA, works fine :)

Signature · 5 lines
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
#6 lore raw
In reply to Vali Cobelea

Hi Vali,

Quoted 8 lines · 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 [email protected]:linux/meta-cgl

Quoted 8 lines

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/

Thanks,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#7 lore raw

Hi,

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.

Best regards,
Vali

Quoted 28 lines · Paul Eggleton

Hi Vali,

Quoted 8 lines · 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 [email protected]:linux/meta-cgl

Quoted 8 lines

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/

Thanks,
Paul

#8 lore raw
Quoted 25 lines · On Wednesday 09 April 2014 13:55:47 Vali Cobelea wrote:
Quoted 15 lines · Paul Eggleton
Quoted 14 lines · 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 [email protected]: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.

Quoted 8 lines
Quoted 2 lines

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/

Quoted 7 lines

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

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#9 lore raw

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

Quoted 42 lines · Paul Eggleton
Quoted 23 lines · On Wednesday 09 April 2014 13:55:47 Vali Cobelea wrote:
Quoted 15 lines · Paul Eggleton
Quoted 14 lines · 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 [email protected]: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.

Quoted 7 lines
Quoted 2 lines

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/

Quoted 7 lines

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

#10 lore raw

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.

Quoted 71 lines · Vali Cobelea

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

Quoted 47 lines · Paul Eggleton
Quoted 27 lines · On Wednesday 09 April 2014 13:55:47 Vali Cobelea wrote:
Quoted 16 lines · Paul Eggleton
Quoted 14 lines · 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 [email protected]: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.

Quoted 9 lines
Quoted 3 lines

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/

Quoted 8 lines

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.

Quoted 4 lines

Cheers,
Paul

--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

#11 lore raw

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"

Let me know how the test goes Deigo.

Best regards,
Vali

Quoted 104 lines · Diego Sueiro

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" <[email protected] <mailto:[email protected]>> 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 [email protected]: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
[email protected] <mailto:[email protected]>
https://lists.yoctoproject.org/listinfo/yocto

#12 lore raw
Quoted 21 lines · Vali Cobelea

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

Quoted 7 lines

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

Quoted 116 lines

Let me know how the test goes Deigo.

Best regards,
Vali

Quoted 105 lines · Diego Sueiro

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" <[email protected] <mailto:[email protected]>> 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 [email protected]: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
[email protected] <mailto:[email protected]>
https://lists.yoctoproject.org/listinfo/yocto

#13 lore raw

Thanks Bruce good observation the BBMASK variable should be:
BBMASK = "meta-security/recipes-security/libcap-ng"

The "meta-cloud-services/meta-openstack/recipes-support/lvm2" was removed because the patch it applies was identic with the one meta-enea applies and it offered an error. Solved this with the last patch.

Alex

-----Original Message-----
From: Bruce Ashfield [mailto:[email protected]]
Sent: Friday, April 11, 2014 3:46 PM
To: Valentin Cobelea; Diego Sueiro
Cc: [email protected]; Alexandru Vaduva; Paul Eggleton
Subject: Re: [yocto] CGL compliance layer initiative

Quoted 26 lines · Vali Cobelea

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-q
t3?topicparent=EETeng.EneaLinuxCGLBuildInstructions;nowysiwyg=0> git clonegit://git.yoctoproject.org/meta-virtualization
<http://twiki.enea.se/twiki/bin/edit/Git://git/yoctoproject/org/Meta-v
irtualization?topicparent=EETeng.EneaLinuxCGLBuildInstructions;nowysiw yg=0> git clonegit://git.yoctoproject.org/meta-selinux
<http://twiki.enea.se/twiki/bin/edit/Git://git/yoctoproject/org/Meta-s
elinux?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-c
loud-services?topicparent=EETeng.EneaLinuxCGLBuildInstructions;nowysiw yg=0> git clonegit://git.yoctoproject.org/meta-security
<http://twiki.enea.se/twiki/bin/edit/Git://git/yoctoproject/org/Meta-s
ecurity?topicparent=EETeng.EneaLinuxCGLBuildInstructions;nowysiwyg=0> git clonehttps://github.com/joaohf/meta-openclovis.git

Quoted 8 lines

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

Quoted 116 lines

Let me know how the test goes Deigo.

Best regards,
Vali

Quoted 105 lines · Diego Sueiro

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" <[email protected] <mailto:[email protected]>> 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 [email protected]: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
[email protected] <mailto:[email protected]>
https://lists.yoctoproject.org/listinfo/yocto

#14 lore raw
In reply to Vali Cobelea

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"
Signature · 2 lines
João Henrique Ferreira de Freitas - joaohf_at_gmail.com
Campinas-SP-Brasil
#15 lore raw

Hi,

Thank you for your kind words.

Quoted 3 lines · João Henrique Ferreira de Freitas

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.

The warnings will be addressed in the upcoming changes. The current state is only the first showcase, an alpha version if you want to call it this way.

Quoted 3 lines

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?

Yes you are right.

Quoted 2 lines

Indeed meta-openclovis has three recipes that could stay in meta-cgl: openhpi, openhpi-subagent and openipmi.

All these are mapped based on our investigation towards few CGL compliance requirements.

Quoted 3 lines

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.

Again, right now we only shown by this layer, in the current state, a direction for what we think could be used in order to start any the CGL compliance for Yocto Project based Linux distros.

Best regards,
Vali

Quoted 30 lines

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"