From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: 宋文武 <iyzsong@member.fsf.org>, "Leo Famulari" <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH]: guix: python-build-system: Change pypi-uri to use https://pypi.io.
Date: Fri, 24 Jun 2016 09:51:56 +1000 [thread overview]
Message-ID: <576C761C.9020106@uq.edu.au> (raw)
In-Reply-To: <87shw4i16t.fsf_-_@member.fsf.org>
On 23/06/16 21:39, 宋文武 wrote:
> Leo Famulari <leo@famulari.name> writes:
>
>> On Wed, Jun 22, 2016 at 01:35:17PM -0500, Christopher Allan Webber wrote:
>>> Note that the old URL scheme no longer seemed to work.
>>>
>>> I'm not thrilled by the new URL "scheme". It seems like more work to
>>> update with each version bump. I'm not sure what the solution is?
>> Please review Ben's 'pypi-origin' patch :)
>>
>> http://lists.gnu.org/archive/html/guix-devel/2016-06/msg00724.html
>>
>>> (source (origin
>>> (method url-fetch)
>>> - (uri (pypi-uri "Flask" version))
>>> + (uri
>>> + (string-append
>>> + "https://pypi.python.org/packages/55/8a/"
>>> + "78e165d30f0c8bb5d57c429a30ee5749825ed461ad6c959688872643ffb3/"
>>> + "Flask-0.11.1.tar.gz"))
>> In the meantime, I think it's best to keep the hash on its own line, to
>> reduce noise in the commit log if we do more updates in this format.
> Ah, nixpkgs use pypi.io for it, and it will redirect the old uri
> scheme to the new one.
>
> I guess we should do the same?
This is a simpler solution than 'pypi-origin'. Thanks.
My only concern is that it is "pre-production", WDYT?
ben
next prev parent reply other threads:[~2016-06-23 23:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 18:35 [PATCH] gnu: python-flask: Update to 0.11.1 Christopher Allan Webber
2016-06-22 18:50 ` Leo Famulari
2016-06-22 22:20 ` Christopher Allan Webber
2016-06-23 11:39 ` [PATCH]: guix: python-build-system: Change pypi-uri to use https://pypi.io 宋文武
2016-06-23 23:51 ` Ben Woodcroft [this message]
2016-06-24 12:14 ` Ludovic Courtès
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=576C761C.9020106@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=guix-devel@gnu.org \
--cc=iyzsong@member.fsf.org \
--cc=leo@famulari.name \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
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.