The current checksums.ini arrangement has a number of issues:
- single monolithic file is a rich source of merge conflicts
- concrete URIs require many duplicate entries for different mirrors
- can be annoying for folks using overlays and/or collections
- storing the checksum separately from t
On Tuesday 10 November 2009 17:55:40 Phil Blundell wrote:
> The current checksums.ini arrangement has a number of issues:
>
> - single monolithic file is a rich source of merge conflicts
> - concrete URIs require many duplicate entries for different mirrors
> - can be annoying for folks using o
2009/11/11 Holger Hans Peter Freyther :
> On Tuesday 10 November 2009 17:55:40 Phil Blundell wrote:
>> The current checksums.ini arrangement has a number of issues:
>>
>> - single monolithic file is a rich source of merge conflicts
>> - concrete URIs require many duplicate entries for different m
On Wed, 2009-11-11 at 02:06 +0100, Holger Hans Peter Freyther wrote:
> SRC_URI = "http://example.org/${PN}-${PV}.tar,bz2";
>
> how do you want to handle these? What happens if you place a checksum in the
> inc file? Do you want to propose removing SRC_URI from .ini files and put
> them
> back t
On Wednesday 11 November 2009 09:24:09 Phil Blundell wrote:
> On Wed, 2009-11-11 at 02:06 +0100, Holger Hans Peter Freyther wrote:
> > SRC_URI = "http://example.org/${PN}-${PV}.tar,bz2";
> >
> > how do you want to handle these? What happens if you place a checksum in
> > the inc file? Do you want t
On Wed, 2009-11-11 at 09:44 +0100, Holger Hans Peter Freyther wrote:
> This will create an even bigger mess. Sometimes you need to download two
> things, this means you will end up with A_MD5SUM, B_MD5SUM, A_SHASUM,
> B_SHASUM. The main problem with the above is that in contrast to a well
> defi
2009/11/11 Phil Blundell :
> On Wed, 2009-11-11 at 09:44 +0100, Holger Hans Peter Freyther wrote:
>> This will create an even bigger mess. Sometimes you need to download two
>> things, this means you will end up with A_MD5SUM, B_MD5SUM, A_SHASUM,
>> B_SHASUM. The main problem with the above is that
On Wednesday 11 November 2009 10:17:42 Phil Blundell wrote:
> On Wed, 2009-11-11 at 09:44 +0100, Holger Hans Peter Freyther wrote:
> > This will create an even bigger mess. Sometimes you need to download two
> > things, this means you will end up with A_MD5SUM, B_MD5SUM, A_SHASUM,
> > B_SHASUM. The
>>There was some discussion around alternative proposals of storing the
>> checksums in separate files within the recipes/ directory.
>> The best alternatives so far where:
>> - Place the checksums into the dir of the recipe
>> - Use a MD5SUM_${URL} = "", SHA256SUM_${URL} = "" syntax
>
Am Mittwoch, den 11.11.2009, 09:17 + schrieb Phil Blundell:
> On Wed, 2009-11-11 at 09:44 +0100, Holger Hans Peter Freyther wrote:
> > This will create an even bigger mess. Sometimes you need to download two
> > things, this means you will end up with A_MD5SUM, B_MD5SUM, A_SHASUM,
> > B_SHASU
On Wed, 2009-11-11 at 10:43 +0100, Holger Hans Peter Freyther wrote:
> On Wednesday 11 November 2009 10:17:42 Phil Blundell wrote:
> > On Wed, 2009-11-11 at 09:44 +0100, Holger Hans Peter Freyther wrote:
> > > This will create an even bigger mess. Sometimes you need to download two
> > > things, th
On Wednesday 11 November 2009 14:31:21 Phil Blundell wrote:
> On Wed, 2009-11-11 at 10:43 +0100, Holger Hans Peter Freyther wrote:
> > On Wednesday 11 November 2009 10:17:42 Phil Blundell wrote:
> > > On Wed, 2009-11-11 at 09:44 +0100, Holger Hans Peter Freyther wrote:
> > It depends. Currently th
On Wednesday 11 November 2009 14:37:46 Holger Hans Peter Freyther wrote:
> On Wednesday 11 November 2009 14:31:21 Phil Blundell wrote:
> > On Wed, 2009-11-11 at 10:43 +0100, Holger Hans Peter Freyther wrote:
> > > On Wednesday 11 November 2009 10:17:42 Phil Blundell wrote:
> > > > On Wed, 2009-11-1
On Wed, 2009-11-11 at 09:44 +0100, Holger Hans Peter Freyther wrote:
> On Wednesday 11 November 2009 09:24:09 Phil Blundell wrote:
> > On Wed, 2009-11-11 at 02:06 +0100, Holger Hans Peter Freyther wrote:
> > > SRC_URI = "http://example.org/${PN}-${PV}.tar,bz2";
> > >
> > > how do you want to handle
On Wed, 2009-11-11 at 14:17 +, Richard Purdie wrote:
> SCR_URI = "xyz://abc.com/efg.tgz;name=bar"
>
> MD5SUM_bar = ""
>
> or maybe :
>
> MD5SUM[bar] = ""
The labelling is a good idea, although I am not especially keen on
either of those notations. How about:
SRC_URI = "xyz://abc.com/efg.t
2009/11/11 Phil Blundell :
> On Wed, 2009-11-11 at 14:17 +, Richard Purdie wrote:
>> SCR_URI = "xyz://abc.com/efg.tgz;name=bar"
>>
>> MD5SUM_bar = ""
>>
>> or maybe :
>>
>> MD5SUM[bar] = ""
>
> The labelling is a good idea, although I am not especially keen on
> either of those notations. How
On Wed, 2009-11-11 at 17:01 +0100, Frans Meulenbroeks wrote:
> 2009/11/11 Phil Blundell :
> > On Wed, 2009-11-11 at 14:17 +, Richard Purdie wrote:
> >> SCR_URI = "xyz://abc.com/efg.tgz;name=bar"
> >>
> >> MD5SUM_bar = ""
> >>
> >> or maybe :
> >>
> >> MD5SUM[bar] = ""
> >
> > The labelling is a
2009/11/11 Phil Blundell :
> On Wed, 2009-11-11 at 17:01 +0100, Frans Meulenbroeks wrote:
>> 2009/11/11 Phil Blundell :
>> > On Wed, 2009-11-11 at 14:17 +, Richard Purdie wrote:
>> >> SCR_URI = "xyz://abc.com/efg.tgz;name=bar"
>> >>
>> >> MD5SUM_bar = ""
>> >>
>> >> or maybe :
>> >>
>> >> MD5SU
On Wed, Nov 11, 2009 at 10:17 AM, Phil Blundell wrote:
> On Wed, 2009-11-11 at 09:44 +0100, Holger Hans Peter Freyther wrote:
>> This will create an even bigger mess. Sometimes you need to download two
>> things, this means you will end up with A_MD5SUM, B_MD5SUM, A_SHASUM,
>> B_SHASUM. The main p
On Wed, 2009-11-11 at 18:37 +0100, Frans Meulenbroeks wrote:
> 2009/11/11 Phil Blundell :
> > On Wed, 2009-11-11 at 17:01 +0100, Frans Meulenbroeks wrote:
> >> 2009/11/11 Phil Blundell :
> >> > On Wed, 2009-11-11 at 14:17 +, Richard Purdie wrote:
> >> >> SCR_URI = "xyz://abc.com/efg.tgz;name=ba
2009/11/11 Phil Blundell :
> On Wed, 2009-11-11 at 18:37 +0100, Frans Meulenbroeks wrote:
>> 2009/11/11 Phil Blundell :
>> > On Wed, 2009-11-11 at 17:01 +0100, Frans Meulenbroeks wrote:
>> >> 2009/11/11 Phil Blundell :
>> >> > On Wed, 2009-11-11 at 14:17 +, Richard Purdie wrote:
>> >> >> SCR_UR
On Wed, Nov 11, 2009 at 7:06 AM, Andrea Adami wrote:
>>>There was some discussion around alternative proposals of storing the
>>> checksums in separate files within the recipes/ directory.
>
>>> The best alternatives so far where:
>>> - Place the checksums into the dir of the recipe
>>>
On Wed, 2009-11-11 at 20:34 +, Phil Blundell wrote:
> That should still work fine. The purpose of the "name=bar" thing is to
> decouple the checksum from the exact URI in use. So, you can write:
>
> SRC_URI = "${MIRROR}/somedir/${PN}-${PV}.tar.gz;name=mytarball \
>${OTHERMIRROR}/
On Thu, Nov 12, 2009 at 06:36:02PM +, Phil Blundell wrote:
>On Wed, 2009-11-11 at 20:34 +, Phil Blundell wrote:
>diff --git a/classes/base.bbclass b/classes/base.bbclass
>index 9d063f2..9508754 100644
>--- a/classes/base.bbclass
>+++ b/classes/base.bbclass
>@@ -56,6 +56,50 @@ def base_chk_
On Thu, 2009-11-12 at 20:18 +0100, Bernhard Reutner-Fischer wrote:
> >+raise Exception("MD5 Sums do not match. Wanted: '%s' Got: '%s'"
> >% (want_md5sum, md5data))
>
> Why are you providing the same information as a note and in the
> exception text?
This is the way those diagnostics
On Thu, 2009-11-12 at 18:36 +, Phil Blundell wrote:
> It turns out that colons in flag names aren't actually accepted by the
> parser, but something similar with dots is OK. So, here's a patch to
> make it work. The modified notation is actually:
>
> SRC_URI[mytarball.md5sum] = "d3b07384d113
On Friday 13 November 2009 18:47:04 Phil Blundell wrote:
> On Thu, 2009-11-12 at 18:36 +, Phil Blundell wrote:
> > It turns out that colons in flag names aren't actually accepted by the
> > parser, but something similar with dots is OK. So, here's a patch to
> > make it work. The modified not
27 matches
Mail list logo
