All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <koen@dominion.kabel.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: content addressable fetching of packages, through MD5SUM or SHA1SUM?
Date: Sun, 02 Mar 2008 20:33:58 +0100	[thread overview]
Message-ID: <fqevf6$8tq$1@ger.gmane.org> (raw)
In-Reply-To: <c384c5ea0803021104s4470cb31o45e1295b7564e876@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Leon Woestenberg schreef:
| Hello,
|
|
| I wonder if someone knows about a content addressable file server, or
| content addressable URL server?
|
| The idea is that the bitbake fetcher does not use the SRC_URI provided
| URL per se, but can fall back to use the SHA1SUM or MD5SUM to ask
| "something" for alternative locations of the package.
|
|
| Such a "server" would implement a two table database:
|
| |authentic file name|md5sum|sha1sum|
|
| (the primary key is |md5sum|sha1sum|)
|
| In a different table, all instances of valid URI that provide this
| content are collected
|
| |md5sum|sha1sum|URI|
|
|
| Now, this might be a Google SoC project, and something that Google
| should have already.

what about:

for archive in * ; do
~   ln -sf $archive $(md5sum $archive)
~   ln -sf $archive $(sha256sum $archive)
done

That's the quick and dirty way :) If someone comes up with a script, I
can run in on the angstrom source mirror for people to test against.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFHywEmMkyGM64RGpERAk6GAKC7coKtqUP26q5zkV9pRc3881A5FACff8hi
XlTJA8PXuOnBxCVRWNNQCt0=
=Kg6V
-----END PGP SIGNATURE-----




  reply	other threads:[~2008-03-02 19:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-02 19:04 content addressable fetching of packages, through MD5SUM or SHA1SUM? Leon Woestenberg
2008-03-02 19:33 ` Koen Kooi [this message]
2008-03-04  9:19   ` Leon Woestenberg
2008-03-04 10:08     ` Leon Woestenberg
2008-03-04 10:31       ` Leon Woestenberg
2008-03-04 10:59         ` Koen Kooi
2008-03-04 11:07         ` Leon Woestenberg
2008-03-03  5:39 ` Rod Whitby

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='fqevf6$8tq$1@ger.gmane.org' \
    --to=koen@dominion.kabel.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.