On 06/01/2012 09:32 PM, McClintock Matthew-B29882 wrote:
On Fri, Jun 1, 2012 at 5:34 AM, David Nyström<david.nyst...@enea.com> wrote:
On 05/31/2012 04:01 PM, Khem Raj wrote:
On Thu, May 31, 2012 at 3:54 AM, David Nyström<david.nyst...@enea.com>
wrote:
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
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.
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
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.
Best Regards,
David
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
