Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/2] base.bbclass: don't pre-generate	checksums.ini entries any longer
Date: Mon, 25 Jan 2010 03:00:24 -0500	[thread overview]
Message-ID: <20100125080024.GB9855@denix.org> (raw)
In-Reply-To: <ac9c93b11001242324g4ef5a426td517f965ffde8720@mail.gmail.com>

On Mon, Jan 25, 2010 at 08:24:11AM +0100, Frans Meulenbroeks wrote:
> 2010/1/25 Khem Raj <raj.khem@gmail.com>:
> > On Sun, Jan 24, 2010 at 5:59 PM, Denys Dmytriyenko <denis@denix.org> wrote:
> >> Signed-off-by: Denys Dmytriyenko <denis@denix.org>
> > OK
> >
> > Acked-by: Khem Raj <raj.khem@gmail.com>
> 
> Do we want to do this at this point? Or say in a week (or two) after
> people got acquainted  to the new format.

Understandable, hence my comment in the summary message:
http://thread.gmane.org/gmane.comp.handhelds.openembedded/29487/focus=29560

The second patch removes the old code to generate missing checksums.ini
entries - can be applied later, once the switch to the new method is
complete and proven.

> Btw: I'm not really a script kiddie, but I guess it should not be too
> difficult to cook up a script to update the recipes so we can abandon
> checksums.ini
> (two mechanisms does not seem to be the right way).
> Any takers?

While it's possible to script, the migration path was defined as to only allow 
deletion from the central checksums.ini file, while adding new checksums in 
the corresponding recipes. Still, converting all the entries from the 
checksums.ini at once would have been a fastest approach.

-- 
Denys



  reply	other threads:[~2010-01-25  9:02 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
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 [this message]
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=20100125080024.GB9855@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