[oe] what to do with wrong checksum

[Otavio Salvador]

Hello,

On Sat, Nov 7, 2009 at 12:42 PM, Koen Kooi <k.kooi at student.utwente.nl> wrote:
> On 07-11-09 14:23, Mike Westerhof wrote:
>>
>> Frans Meulenbroeks wrote:
>> ...
>>>
>>> Reluctantly updated checksums.ini
>>>
>>> Frans
>>
>> But of course there's no magic that will remove the old cached tarball
>> out of one's downloads directory when this sort of thing happens.
>> (Busybox has been known to do this, too)
>>
>> What do folks think we should do about that when it occurs?
>> a) support two entries (old and new) in checksums.ini
>> b) do nothing (leave as is)
>> c) add some sort of support so that the user gets additional information
>>    with the new checksum match failure explaining that the checksum was
>>    updated and they need to manually remove the old (bad) tarball
>
> d) rename the tarball slighty and mirror in on a known good server (e.g.
> angstrom sourcemirror) and have OE use that.

IMO (d) is the safest and the right thing to do; this avoids more core
to be written and avoids also we use changed versions without
noticing.

-- 
Otavio Salvador                  O.S. Systems
E-mail: otavio at ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854         http://projetos.ossystems.com.br