All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: checksums.ini - should check only against filename not uri_src
Date: Sun, 19 Oct 2008 17:55:16 +0200	[thread overview]
Message-ID: <gdfl94$866$1@ger.gmane.org> (raw)
In-Reply-To: <c384c5ea0810181249x4d700cdbw2e409eb1fecefaab@mail.gmail.com>

On 18-10-2008 21:49, Leon Woestenberg wrote:
> Hello,
>
> On Sat, Oct 18, 2008 at 8:30 PM, Martin Jansa<Martin.Jansa@mk.cvut.cz>  wrote:
>> On Fri, Oct 17, 2008 at 08:41:09PM +0200, Marcin Juszkiewicz wrote:
>> could be used. From discussion on irc it seemed like global checksums.ini
>> is not a good idea at all, at least because of high probability of merge
>> conflicts, and that checksums should be moved to .bb files or defined on
>> per-package files.
>>
> Yes, I agree the checksums solution should be redesigned.
>
>
> Note that I have written a package to help import, learn and
> automatically google for missing packages, from which some ideas might
> be ripped.

Could we use it in OE as do_fetch error handler? If we know the sha256 
sum of a package it is safe to pull it from a semi-random place on the 
net when debian cleans out their archive again.

regards,

Koen


>
> Source here:
>
> http://www.sidebranch.com/leon/witpa_20080730.tar.bz2
>
> Regards,





  reply	other threads:[~2008-10-19 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 13:17 checksums.ini - should check only against filename not uri_src Martin Jansa
2008-10-17 18:41 ` Marcin Juszkiewicz
2008-10-18 18:30   ` Martin Jansa
2008-10-18 19:49     ` Leon Woestenberg
2008-10-19 15:55       ` Koen Kooi [this message]
2008-10-20 20:21         ` Leon Woestenberg

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='gdfl94$866$1@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.