From: Leo Famulari <leo@famulari.name>
To: Christopher Allan Webber <cwebber@dustycloud.org>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Source tarballs from PyPI versus tarballs from the individual project websites
Date: Wed, 12 Oct 2016 10:13:03 -0400 [thread overview]
Message-ID: <20161012141303.GB18017@jasmine> (raw)
In-Reply-To: <87a8e9dbkn.fsf@dustycloud.org>
On Wed, Oct 12, 2016 at 06:57:28AM -0500, Christopher Allan Webber wrote:
> I'd be for using actual upstream, or at least supplying both, so that
> they're mirrors. One concern is, what about the tooling for telling us
> when updates to packages are available?
I've noticed that the PyPi tarballs and the "upstream site" tarballs are
usually not the same thing. So, you could ask upstream what the prefer
packagers use and pick that one.
prev parent reply other threads:[~2016-10-12 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 6:16 Source tarballs from PyPI versus tarballs from the individual project websites Arun Isaac
2016-10-12 7:49 ` Alex Kost
2016-10-12 11:57 ` Christopher Allan Webber
2016-10-12 12:44 ` Ludovic Courtès
2016-10-12 14:52 ` Arun Isaac
2016-10-12 20:15 ` Ludovic Courtès
2016-10-12 14:13 ` 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=20161012141303.GB18017@jasmine \
--to=leo@famulari.name \
--cc=cwebber@dustycloud.org \
--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).