All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: checksums situation
Date: Wed, 25 Feb 2009 09:01:48 +0000	[thread overview]
Message-ID: <1235552508.5399.2.camel@dax.rpnet.com> (raw)
In-Reply-To: <20090225022507.GP2172@smtp.west.cox.net>


On Tue, 2009-02-24 at 19:25 -0700, Tom Rini wrote:
> On Tue, Feb 24, 2009 at 11:01:05PM -0300, Otavio Salvador wrote:
> [snip]
> > I do belive that the best way to solve it is to have a md5 file together
> > with the .bb recipe. This solves the problems for forks, derivatives and
> > also makes harder to just use "cat tmp/checksums.ini >> conf/checksums.ini".
> 
> Running a script that will make the .sum file isn't any harder really.
> And it's still a "this is the checksum we downloaded" not "this is the
> checksum upstream says is correct".

You can specify the md5 as part of the SRC_URI if I remember correctly.
Its just such a pain, nobody does.

-- 
RP




  reply	other threads:[~2009-02-25  9:03 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 16:28 checksums situation Marcin Juszkiewicz
2009-02-13 17:08 ` Otavio Salvador
2009-02-13 17:39   ` Ihar Hrachyshka
2009-02-13 18:37     ` Otavio Salvador
2009-02-13 19:35       ` Leon Woestenberg
2010-02-12 18:45         ` mike
2009-02-13 19:41       ` John Willis
2009-02-15 10:04       ` Phil Blundell
2009-02-15 18:32         ` Otavio Salvador
2009-02-13 17:09 ` Tom Rini
2009-02-13 17:28 ` Andrea Adami
2009-02-13 17:34   ` Andrea Adami
2009-02-13 18:02 ` Koen Kooi
2009-02-14 14:51 ` Yuri Bushmelev
2009-02-24  6:46 ` Tom Rini
2009-02-24  6:51   ` Tom Rini
2009-02-24  8:49   ` Marcin Juszkiewicz
2009-02-24 15:02     ` Tom Rini
2009-02-24 16:13   ` Michael 'Mickey' Lauer
2009-02-24 16:25     ` Angus Ainslie
2009-02-24 16:37       ` Tom Rini
2009-02-24 16:28     ` Philip Balister
2009-02-24 16:36       ` Tom Rini
2009-02-24 22:10       ` GNUtoo
2009-02-24 22:17         ` Tom Rini
2009-02-24 22:29         ` Phil Blundell
2009-02-24 22:42           ` GNUtoo
2009-02-25  9:09           ` Richard Purdie
2009-02-25 23:04             ` Denys Dmytriyenko
2009-02-26 13:28               ` Richard Purdie
2009-02-27  0:20                 ` Otavio Salvador
2009-02-24 18:01     ` Otavio Salvador
2009-02-24 18:36       ` Ihar Hrachyshka
2009-02-24 18:50         ` Tom Rini
2009-02-24 22:20           ` GNUtoo
2009-02-25  2:01           ` Otavio Salvador
2009-02-25  2:25             ` Tom Rini
2009-02-25  9:01               ` Richard Purdie [this message]
2009-02-25 21:27               ` Vitus Jensen
2009-02-25 21:35                 ` Tom Rini
2009-02-25 22:04                   ` Vitus Jensen
2009-02-26  8:10                     ` Koen Kooi
2009-02-26 12:50                   ` Bernhard Guillon
2009-02-28  9:57                     ` Alessandro GARDICH
2009-02-28 10:45                       ` Koen Kooi
2009-02-28 10:51                         ` Alessandro GARDICH
2009-02-28 13:12                           ` Philip Balister
2009-02-24 20:29 ` Bernhard Guillon
2009-02-24 22:45   ` GNUtoo
2009-02-25  9:16 ` Koen Kooi
  -- strict thread matches above, loose matches on Subject: below --
2009-02-24 20:00 Frans Meulenbroeks

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=1235552508.5399.2.camel@dax.rpnet.com \
    --to=rpurdie@rpsys.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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 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.