PR and bbappends

Hi All,

Is there a good way to get the layer name ?, I want to add PR .= "+${LAYER_NAME}.0" to my bbappends for clarity and versioning when having multiple meta layers.
Where a bbappend:s on package X can reside in one, two or more layers.

Best Regards,
David

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

Quoted 7 lines · David Nyström

Hi All,

Is there a good way to get the layer name ?, I want to add PR .= "+${LAYER_NAME}.0" to my bbappends for clarity and versioning when having multiple meta layers.
Where a bbappend:s on package X can reside in one, two or more layers.

you could look into bitbake-layers tool bitbake-layers show-overlayed will show the recipes overlays if thats the problem you are trying to solve

Quoted 7 lines

Best Regards,
David

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

Quoted 6 lines · Khem Raj

Quoted 3 lines · David Nyström

Hi All,

Quoted 9 lines

Quoted 5 lines

Is there a good way to get the layer name ?, I want to add PR .= "+${LAYER_NAME}.0" to my bbappends for clarity and versioning when having multiple meta layers.
Where a bbappend:s on package X can reside in one, two or more layers.

you could look into  bitbake-layers tool bitbake-layers show-overlayed will show the recipes overlays if thats the problem you are trying to solve

Thanks, I was unaware of that script. But not really want I want to do. We are going to have multiple BSP layers sourced from BSP suppliers, and customer specific layers on top of this.
When it comes to testing, we want our test-objects(binary packages) to differ depending on which layers appended them,
so that we can easily automate a testing procedure, and reduce possible permutations of testobjects.(For unit testing).

Also, when you see bash_4.2-r2+meta-fsl-ppc.0+meta-ti.2_ppce500mc.ipk, you directly see who manipulated the contents
of the bash package. And where eventual failures could originate from.

Quoted 22 lines · David Nyström

Quoted 4 lines · Khem Raj

Quoted 2 lines · David Nyström

Hi All,

Quoted 9 lines

Quoted 5 lines

Is there a good way to get the layer name ?, I want to add PR .= "+${LAYER_NAME}.0" to my bbappends for clarity and versioning when having multiple meta layers.
Where a bbappend:s on package X can reside in one, two or more layers.

you could look into bitbake-layers tool bitbake-layers show-overlayed will show the recipes overlays if thats the problem you are trying to solve

Thanks, I was unaware of that script. But not really want I want to do. We are going to have multiple BSP layers sourced from BSP suppliers, and customer specific layers on top of this.
When it comes to testing, we want our test-objects(binary packages) to differ depending on which layers appended them,
so that we can easily automate a testing procedure, and reduce possible permutations of testobjects.(For unit testing).

Quoted 3 lines

Also, when you see bash_4.2-r2+meta-fsl-ppc.0+meta-ti.2_ppce500mc.ipk, you directly see who manipulated the contents
of the bash package. And where eventual failures could originate from.

Some based layers should not modify certain packages. Which meta-fsl-ppc is guilty of doing which I would like to cleanup. Changes to packages should be moved up to a distro layer I believe?

-M

Quoted 3 lines · On 06/01/2012 09:32 PM, McClintock Matthew-B29882 wrote:

Some based layers should not modify certain packages. Which meta-fsl-ppc is guilty of doing which I would like to cleanup. Changes to packages should be moved up to a distro layer I believe?

I don't mind BSP layers modifying packages, as long as its called for. It would be helpful if BSP maintainers could try to enforce those bbappends only on machines in the BSP layer itself. i.e.

Bugfix and other similar bbappends on generic stuff could be placed in a separate directory which can be easily BBMASK:ed.