unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ben Woodcroft <donttrustben@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: pypi URL change
Date: Wed, 27 Apr 2016 14:25:38 +0200	[thread overview]
Message-ID: <87oa8v2q7x.fsf@gnu.org> (raw)
In-Reply-To: <571F551C.9040503@gmail.com> (Ben Woodcroft's message of "Tue, 26 Apr 2016 21:46:36 +1000")

Ben Woodcroft <donttrustben@gmail.com> skribis:

> Hmm. It just dawned on me that it is impossible to implement the
> pypi-uri so that it returns the new format because the new URI is
> generated from the content of the package, not just the name and
> version.

Oh indeed.

> So I think we must either write the hash or the entire URL into the
> package, or grab the json from pypi each time we download.

The former, I guess.

I guess the hash is SHA1, right?

Maybe we could make something like:

  (define-syntax-rule (pypi-origin package sha1 sha256-string)
    (origin
      (method url-fetch)
      (uri (string-append … sha1 …))
      (sha256 (base32 sha256-string))))

and then use it like:

  (package
    (name "python-foo")
    (source (pypi-origin "foo" "cabba9e" "somelongstring")))

?

Ludo’.

  reply	other threads:[~2016-04-27 12:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-24  7:27 pypi URL change Ben Woodcroft
2016-04-24 22:26 ` Cyril Roelandt
2016-04-24 23:21   ` Ben Woodcroft
2016-04-25  0:13     ` Cyril Roelandt
2016-04-25  1:44       ` Ben Woodcroft
2016-04-25  7:54       ` Ludovic Courtès
2016-04-26 11:46         ` Ben Woodcroft
2016-04-27 12:25           ` Ludovic Courtès [this message]
2016-06-17 22:33             ` Ben Woodcroft
2016-06-17 22:33               ` [PATCH 1/3] build-system/python: Add pypi-origin Ben Woodcroft
2016-06-17 22:33               ` [PATCH 2/3] gnu: Add python-screed Ben Woodcroft
2016-06-25 17:44                 ` Leo Famulari
2016-06-17 22:33               ` [PATCH 3/3] not a real patch Ben Woodcroft

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87oa8v2q7x.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=donttrustben@gmail.com \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).