Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Official policy to list checksums
Date: Sun, 24 Jan 2010 02:06:02 -0500	[thread overview]
Message-ID: <20100124070602.GA8642@denix.org> (raw)
In-Reply-To: <1264277173.3738.74.camel@mattotaupa.wohnung.familie-menzel.net>

On Sat, Jan 23, 2010 at 09:06:13PM +0100, Paul Menzel wrote:
> does [1] still describe the official policy to add checksums? Or is

No

> putting them into the recipes preferred nowadays?

Yes

> For example
> 
>         SRC_URI[whois.md5sum] = "18d74a07d711262b75f04a1c319bc833"
>         SRC_URI[whois.sha256sum] = "fb13316c09ff9f98bd9af659d0789c9a09b97757f5c6c3dbfbc790250d5c5abc"

Please read "Death by checksums" thread here:
http://thread.gmane.org/gmane.comp.handhelds.openembedded/27465

-- 
Denys



  reply	other threads:[~2010-01-24  7:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-23 20:06 Official policy to list checksums Paul Menzel
2010-01-24  7:06 ` Denys Dmytriyenko [this message]
2010-01-24 10:29   ` Koen Kooi
2010-01-24 11:08     ` Frans Meulenbroeks
2010-01-24 11:13       ` Koen Kooi
2010-01-24 11:25         ` Paul Menzel
2010-01-25  1:56     ` Denys Dmytriyenko
2010-01-25  1:59       ` [PATCH 0/2] simplify switch to new SRC_URI-based checksums Denys Dmytriyenko
2010-01-25  1:59       ` [PATCH 1/2] base.bbclass: pre-create SRC_URI checksums to include in the recipe Denys Dmytriyenko
2010-01-25  7:17         ` Khem Raj
2010-01-25  7:19         ` Frans Meulenbroeks
2010-01-25  1:59       ` [PATCH 2/2] base.bbclass: don't pre-generate checksums.ini entries any longer Denys Dmytriyenko
2010-01-25  7:18         ` Khem Raj
2010-01-25  7:24           ` Frans Meulenbroeks
2010-01-25  8:00             ` Denys Dmytriyenko
2010-01-25  7:24       ` Official policy to list checksums Khem Raj
2010-01-25  8:19       ` Koen Kooi
2010-01-25  8:43         ` Denys Dmytriyenko
2010-01-25  8:52           ` Graeme Gregory
2010-01-27 22:09             ` Denys Dmytriyenko
2010-02-21 10:37               ` Frans Meulenbroeks
2010-01-25  9:55           ` Koen Kooi

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=20100124070602.GA8642@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox