From: Scott Garman <scott.a.garman@intel.com>
To: <yocto@yoctoproject.org>
Subject: Re: BKM on add SRC_URI MD5 and SHA256 checksum
Date: Wed, 17 Nov 2010 18:42:25 -0800 [thread overview]
Message-ID: <4CE49291.7020706@intel.com> (raw)
In-Reply-To: <33AB447FBD802F4E932063B962385B3530383DDA@shsmsx501.ccr.corp.intel.com>
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"
>
> The md5sum and sha256sum value can be get by:
>
> # md5sum /your_DL_DIR/ tar-1.23.tar.bz2
> 41e2ca4b924ec7860e51b43ad06cdb7e
>
> # sha256sum /your_DL_DIR/ tar-1.23.tar.bz2
> c9328372db62fbb1d94c9e4e3cefc961111af46de47085b635359c00a0eebe36
Thanks Ke,
As a style note I'll mention that the usual place to put the entries in
a recipe is after the SRC_URI line. Example:
http://git.pokylinux.org/cgit/cgit.cgi/poky/tree/meta/recipes-extended/grep/grep_2.7.bb
I tend to put a blank line between the SRC_URI and SRC_URI[checksum]
fields, but that's just my personal preference. I think it looks best
especially when a SRC_URI includes several patches.
Scott
--
Scott Garman
Embedded Linux Distro Engineer - Yocto Project
next prev parent reply other threads:[~2010-11-18 2:43 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 [this message]
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
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=4CE49291.7020706@intel.com \
--to=scott.a.garman@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.