* PR and bbappends
@ 2012-05-31 10:54 David Nyström
2012-05-31 14:01 ` Khem Raj
0 siblings, 1 reply; 6+ messages in thread
From: David Nyström @ 2012-05-31 10:54 UTC (permalink / raw)
To: yocto@yoctoproject.org
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: PR and bbappends 2012-05-31 10:54 PR and bbappends David Nyström @ 2012-05-31 14:01 ` Khem Raj 2012-06-01 10:34 ` David Nyström 0 siblings, 1 reply; 6+ messages in thread From: Khem Raj @ 2012-05-31 14:01 UTC (permalink / raw) To: David Nyström; +Cc: yocto@yoctoproject.org On Thu, May 31, 2012 at 3:54 AM, David Nyström <david.nystrom@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 > Best Regards, > David > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: PR and bbappends 2012-05-31 14:01 ` Khem Raj @ 2012-06-01 10:34 ` David Nyström 2012-06-01 19:32 ` McClintock Matthew-B29882 0 siblings, 1 reply; 6+ messages in thread From: David Nyström @ 2012-06-01 10:34 UTC (permalink / raw) To: Khem Raj; +Cc: yocto@yoctoproject.org On 05/31/2012 04:01 PM, Khem Raj wrote: > On Thu, May 31, 2012 at 3:54 AM, David Nyström<david.nystrom@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. >> Best Regards, >> David >> >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: PR and bbappends 2012-06-01 10:34 ` David Nyström @ 2012-06-01 19:32 ` McClintock Matthew-B29882 2012-06-04 8:12 ` David Nyström 0 siblings, 1 reply; 6+ messages in thread From: McClintock Matthew-B29882 @ 2012-06-01 19:32 UTC (permalink / raw) To: David Nyström; +Cc: yocto@yoctoproject.org On Fri, Jun 1, 2012 at 5:34 AM, David Nyström <david.nystrom@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.nystrom@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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: PR and bbappends 2012-06-01 19:32 ` McClintock Matthew-B29882 @ 2012-06-04 8:12 ` David Nyström 2012-06-10 22:04 ` Paul Eggleton 0 siblings, 1 reply; 6+ messages in thread From: David Nyström @ 2012-06-04 8:12 UTC (permalink / raw) To: McClintock Matthew-B29882; +Cc: yocto@yoctoproject.org On 06/01/2012 09:32 PM, McClintock Matthew-B29882 wrote: > On Fri, Jun 1, 2012 at 5:34 AM, David Nyström<david.nystrom@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.nystrom@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 ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: PR and bbappends 2012-06-04 8:12 ` David Nyström @ 2012-06-10 22:04 ` Paul Eggleton 0 siblings, 0 replies; 6+ messages in thread From: Paul Eggleton @ 2012-06-10 22:04 UTC (permalink / raw) To: yocto; +Cc: McClintock Matthew-B29882 On Monday 04 June 2012 10:12:09 David Nyström wrote: > 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. If they're bugfixes that are not in any way machine-specific they really do not belong in the BSP. They're fine for distro layers, although I would strongly encourage people to be pushing these fixes up to OE-core unless they are specific to some distro policy. FYI, for machine specific changes in bbappends you can still make use of a machine override to ensure that the change only applies when building for that specific machine. With a lot of variable changes that could get messy though :/ Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-06-10 22:04 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-05-31 10:54 PR and bbappends David Nyström 2012-05-31 14:01 ` Khem Raj 2012-06-01 10:34 ` David Nyström 2012-06-01 19:32 ` McClintock Matthew-B29882 2012-06-04 8:12 ` David Nyström 2012-06-10 22:04 ` Paul Eggleton
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.