From: Tom Rini <trini@kernel.crashing.org>
To: openembedded-devel@openembedded.org
Subject: Re: checksums situation
Date: Mon, 23 Feb 2009 23:51:24 -0700 [thread overview]
Message-ID: <20090224065124.GF2172@smtp.west.cox.net> (raw)
In-Reply-To: <20090224064639.GE2172@smtp.west.cox.net>
On Mon, Feb 23, 2009 at 11:46:39PM -0700, Tom Rini wrote:
> On Fri, Feb 13, 2009 at 05:28:08PM +0100, Marcin Juszkiewicz wrote:
>
> >
> > Hi
> >
> > It is nearly two years since conf/checksums.ini was introduced. We
> > populated it with over 6000 entries during that time (mostly by
> > automatic fetching of all source on CELF and EWI machines). But there
> > are problems with it's format.
>
> I'm going to make a different suggestion. Lets just drop it. Part of
> why I say this is that we went back on it being a mandatory thing
> because it was a burden. And we're already back to adding stuff without
> checksums again (gstreamer, libdaemon on this build so far..).
[snip]
> Oh, and in the 5 minutes the above took to write, gst-plugins-base
> failed to have a checksum too.
OK, this is a me problem. But the rest of my point stands. I'm willing
to bet most people aren't making sure the md5/sha1 is right with
upstream, and I think we'd be better off at trying to automatically grab
an upstream verification and use that.
--
Tom Rini
next prev parent reply other threads:[~2009-02-24 6:54 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 [this message]
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
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=20090224065124.GF2172@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--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.