From: Leo Famulari <leo@famulari.name>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add python-xopen.
Date: Fri, 16 Dec 2016 15:19:11 -0500 [thread overview]
Message-ID: <20161216201911.GJ20488@jasmine> (raw)
In-Reply-To: <9d677194-d2a5-51b1-cd00-b3edeaa6b45c@tobias.gr>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
On Thu, Dec 15, 2016 at 11:02:29AM +0100, Tobias Geerinckx-Rice wrote:
> Marius,
>
> On 15/12/16 10:20, Marius Bakke wrote:
> > Why not use 'pypi-uri' here? Otherwise LGTM.
>
> What would that give us?
From what I can tell, GitHub automatically generates snapshot tarballs
of Git tags. These tarballs are usually not real "release" tarballs that
have been prepared by the upstream maintainers. Sometimes this isn't the
case, but it seems to be for these "untitled" v$version.tar.gz tarballs.
We have tools to automatically update packages fetched from PyPi.
And using pypi-uri removes another URL that we need to maintain.
Is there a reason not to use PyPi?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2016-12-16 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 22:57 [PATCH] gnu: Add python-xopen Tobias Geerinckx-Rice
2016-12-15 9:20 ` Marius Bakke
2016-12-15 10:02 ` Tobias Geerinckx-Rice
2016-12-16 16:09 ` Marius Bakke
2016-12-18 1:00 ` Tobias Geerinckx-Rice
2016-12-18 1:23 ` Ben Woodcroft
2016-12-18 10:07 ` Hartmut Goebel
2016-12-18 16:21 ` Tobias Geerinckx-Rice
2016-12-16 20:19 ` Leo Famulari [this message]
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=20161216201911.GJ20488@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).