From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Checksums.ini again - new format this time
Date: Tue, 10 Nov 2009 06:39:46 -0500 [thread overview]
Message-ID: <20091110113946.GA24738@denix.org> (raw)
In-Reply-To: <20091109065322.GD16449@ibawizard.net>
On Mon, Nov 09, 2009 at 07:53:22AM +0100, Petr ?tetiar wrote:
> Holger Hans Peter Freyther <holger+oe@freyther.de> [2009-11-02 03:09:56]:
>
> > On Sunday 01 November 2009 23:59:18 Andrea Adami wrote:
> > > And what about having a checksum file in each dir of /recipes ?
> > > If the checksum changes the PR should be changed too.
> >
> >
> > I think that is the best way in terms of scalability and BB collections. We
> > have some weird cases where we might do require ../ but these are broken or
> > need to duplicate the checksums...
>
> I like this idea more than one monolitic checksum file. checksums.ini is place
> for storing of a duplicate information anyway. You need to enter URL in checksums,
> you need to enter URL again into recipe.
>
> Wouldn't it be better to write URL with checksum once at one place and reuse
> it than in recipe as some kind of variable or something like that?
It was discussed during OEDEM and the conclusion was to switch to using
checksums in SRC_URIs of corresponding recipes.
--
Denys
next prev parent reply other threads:[~2009-11-10 12:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 11:41 Checksums.ini again - new format this time Marcin Juszkiewicz
2009-10-29 11:43 ` Phil Blundell
2009-10-29 13:19 ` Koen Kooi
2009-11-01 17:42 ` Koen Kooi
2009-11-01 20:35 ` Leon Woestenberg
2009-11-01 22:59 ` Andrea Adami
2009-11-02 2:09 ` Holger Hans Peter Freyther
2009-11-09 6:53 ` Petr Štetiar
2009-11-10 11:39 ` Denys Dmytriyenko [this message]
2009-11-02 2:06 ` Holger Hans Peter Freyther
2009-11-02 8:41 ` Koen Kooi
2009-11-02 9:07 ` Holger Hans Peter Freyther
2009-11-02 9:26 ` Leon Woestenberg
2009-11-02 9:19 ` Marcin Juszkiewicz
2009-11-02 9:18 ` Marcin Juszkiewicz
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=20091110113946.GA24738@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 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.