unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: pypi URL change
Date: Mon, 25 Apr 2016 09:54:39 +0200	[thread overview]
Message-ID: <87y482azsw.fsf@gnu.org> (raw)
In-Reply-To: <571D612E.7000802@gmail.com> (Cyril Roelandt's message of "Mon, 25 Apr 2016 02:13:34 +0200")

Cyril Roelandt <tipecaml@gmail.com> skribis:

> On 04/25/2016 01:21 AM, Ben Woodcroft wrote:
>> 2) The new URLs are even uglier than the old one and a working pypi-uri 
>> would hide them from our eyes.
>
> Yeah but it is my understanding that the new pattern will only be
> applied to new releases, so how will pypi-uri know what pattern to apply?

How about changing ‘pypi-uri’ to return two URIs, the new one and the
old one, in this order?

That way, attempts to download will first try the first URI, then the
second.

Alternately, we could define a “pypi” mirror in (guix download) that
would contain at least these two URIs, and have ‘pypi-uri’ return
“mirror://pypi/…”.  That only works if the two URIs share the same
suffix, though.

WDYT?

Ludo’.

  parent reply	other threads:[~2016-04-25  7:54 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 [this message]
2016-04-26 11:46         ` Ben Woodcroft
2016-04-27 12:25           ` Ludovic Courtès
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=87y482azsw.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=tipecaml@gmail.com \
    /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).