All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: yocto@yoctoproject.org
Subject: Re: BSPs and duplicate files
Date: Fri, 12 Nov 2010 09:42:51 -0800	[thread overview]
Message-ID: <ibjuar$74b$1@dough.gmane.org> (raw)
In-Reply-To: <4CDCBB73.3010303@intel.com>

On 11/11/2010 07:58 PM, Scott Garman wrote:
> On 11/11/2010 04:16 PM, Philip Balister wrote:
>> On 11/11/2010 07:19 AM, João Henrique Freitas wrote:
>>> Hi,
>>>
>>> Two questions:
>>>
>>> With some BSPs, like
>>>
>>> meta
>>> meta-myhardware
>>> meta-mydistro
>>>
>>> I need to create a conf/checksums.ini for every BSP or append it to
>>> meta/conf/checksums.ini ? In other others, checksums.ini is per BSP or
>>> unique?
>>
>> Poky still uses checksums.ini? OE moved the checksums to the recipes and
>> this seems make things much easier to work with.
>
> We'll be switching to recipe-based checksums soon in master, and in fact
> you'll notice that most of our recipes already have checksums in them.
> It's just a matter of importing the code from OE and making whatever
> tweaks might be necessary.

Good to know. I don't think one approach is technically better than the 
other, but when you have a "large" community, it seemed like one 
checksum file lead to merge conflicts.

Philip



      reply	other threads:[~2010-11-12 17:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-11 15:19 BSPs and duplicate files João Henrique Freitas
2010-11-11 15:38 ` Joshua Lock
2010-11-11 21:39   ` João Henrique Freitas
2010-11-12  0:16 ` Philip Balister
2010-11-12  3:58   ` Scott Garman
2010-11-12 17:42     ` Philip Balister [this message]

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='ibjuar$74b$1@dough.gmane.org' \
    --to=philip@balister.org \
    --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.