All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: yocto@yoctoproject.org
Subject: Re: BKM on add SRC_URI MD5 and SHA256 checksum
Date: Thu, 18 Nov 2010 10:49:00 +0000	[thread overview]
Message-ID: <1290077340.2487.0.camel@scimitar> (raw)
In-Reply-To: <4CE4B9DC.9050003@intel.com>

On Wed, 2010-11-17 at 21:30 -0800, Scott Garman wrote:
> On 11/17/2010 09:10 PM, Saul Wold wrote:
> > On 11/17/2010 06:32 PM, Yu, Ke wrote:
> >> Hi Distro folks:
> >>
> >> As Saul suggest to add SRC_URI MD5 and SHA256 checksum when we upgrade the recipes, here is a simple how-to:
> >>
> >> Two entry is needed for checksum, take meta/recipes-extended/tar/tar_1.23.bb as example:
> >> SRC_URI[md5sum] = "41e2ca4b924ec7860e51b43ad06cdb7e"
> >> SRC_URI[sha256sum] = "c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36"
> >>
> > Also, a clarification, these values should go at the END of the file,
> > which I believe is the OE Style on this.
> 
> The reason you see many OE files with the checksums at the end of the 
> file is that at one point a member of the OE community wrote a script to 
> append the values to a ton of recipes and then checked it in.
> 
> I would think that keeping the SRC_URI fields relatively close to each 
> other makes more logical sense. But I'm not going to get religious about it.

I'm willing to be religious about it. A selling point of Poky has always
been the cleaner, better maintained, metadata. 

Therefore fields which logically fit together should be kept so. Let's
keep the SRC_URI fields together please.

Cheers,
Joshua
-- 
Joshua Lock
        Intel Open Source Technology Centre



      parent reply	other threads:[~2010-11-18 10:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  2:32 BKM on add SRC_URI MD5 and SHA256 checksum Yu, Ke
2010-11-18  2:42 ` Scott Garman
2010-11-18  5:10 ` Saul Wold
2010-11-18  5:30   ` Scott Garman
2010-11-18  5:35     ` Saul Wold
2010-11-18  5:13       ` Yu Ke
2010-11-18 16:54       ` Scott Garman
2010-11-18 10:49     ` Joshua Lock [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=1290077340.2487.0.camel@scimitar \
    --to=josh@linux.intel.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.