From: Alex Kost <alezost@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
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:49:04 +0300 [thread overview]
Message-ID: <87vawyvwgf.fsf@gmail.com> (raw)
In-Reply-To: <cu7oa2qdrda.fsf@systemreboot.net> (Arun Isaac's message of "Wed, 12 Oct 2016 11:46:17 +0530")
Arun Isaac (2016-10-12 11:46 +0530) wrote:
> When packaging python packages, why are we using the source tarballs
> hosted on PyPI, rather than using the source tarballs hosted on the
> websites of the individual projects?
>
> For example, for the package python-pycrypto, why are we using the
> tarball from PyPI
> https://pypi.python.org/packages/source/p/pycrypto/pycrypto-2.6.1.tar.gz
> instead of the tarball from the pycrypto project website
> https://ftp.dlitz.net/pub/dlitz/crypto/pycrypto/pycrypto-2.6.1.tar.gz ?
>
> Using the PyPI tarball seems to make Guix dependent on another package
> repository -- namely, PyPI. That seems to me a bad thing.
>
> I have packaged a few python packages using the tarballs from their
> respective project websites. Should I change them to use the PyPI
> tarballs before contributing the package definitions to Guix? Which
> tarball should I prefer?
As for me, I always prefer tarballs directly from the upstream. So I
wouldn't change those packages to use PyPi sources.
--
Alex
next prev parent reply other threads:[~2016-10-12 7:49 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 [this message]
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
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=87vawyvwgf.fsf@gmail.com \
--to=alezost@gmail.com \
--cc=arunisaac@systemreboot.net \
--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 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.