Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Official policy to list checksums
Date: Sun, 24 Jan 2010 11:29:56 +0100	[thread overview]
Message-ID: <hjh7f3$6v0$2@ger.gmane.org> (raw)
In-Reply-To: <20100124070602.GA8642@denix.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 24-01-10 08:06, Denys Dmytriyenko wrote:
> 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

I think not! The new format:

* is not documented
* it has no tools to autogenerate it
* has not been agreed on in any way.

As an experiment I tried to use it for a branch at work and I
*absolutely* hate the workflow needed for the new format.

With checksums.ini it's a matter of:

either

cat /OE/tmp/checksums.ini >> conf/checksums.ini ; python
contrib/source-checker/oe-checksum-sorter -i conf/checksums.ini

or

Verbatimly copy/paste the *output* OE gives you into conf/checksums.ini.

These concerns have been raised time after time and still haven't been
addressed, so for now:

checksums.ini is the way to go
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLXCEkMkyGM64RGpERAsSuAKCL8RKc/w03gNou79d3HXJbf8wqtACgnkrn
0jZ/RL/sSIoBxyLT4vGaMdc=
=K1O3
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-01-24 10:32 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
2010-01-24 10:29   ` Koen Kooi [this message]
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='hjh7f3$6v0$2@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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