All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Nyström" <david.nystrom@enea.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: PR and bbappends
Date: Fri, 1 Jun 2012 12:34:25 +0200	[thread overview]
Message-ID: <4FC89AB1.40706@enea.com> (raw)
In-Reply-To: <CAMKF1soZ7Ss7s245Y4xtGBypheW5RSDgJMCRAr1FG2xF5cE3-w@mail.gmail.com>

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



  reply	other threads:[~2012-06-01 10:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2012-06-01 19:32     ` McClintock Matthew-B29882
2012-06-04  8:12       ` David Nyström
2012-06-10 22:04         ` Paul Eggleton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FC89AB1.40706@enea.com \
    --to=david.nystrom@enea.com \
    --cc=raj.khem@gmail.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.