Re: Source tarballs from PyPI versus tarballs from the individual project websites

2016-10-12 Thread Ludovic Courtès
Arun Isaac skribis: >>> One concern is, what about the tooling for telling us when updates to >>> packages are available? >> >> ‘guix refresh’ works for PyPI but not for arbitrary sites. > > Why not let 'guix refresh' use PyPI to detect package updates, and then > let somebody manually find the e

Re: Source tarballs from PyPI versus tarballs from the individual project websites

2016-10-12 Thread Arun Isaac
>> One concern is, what about the tooling for telling us when updates to >> packages are available? > > ‘guix refresh’ works for PyPI but not for arbitrary sites. Why not let 'guix refresh' use PyPI to detect package updates, and then let somebody manually find the equivalent upstream tarball URI

Re: Source tarballs from PyPI versus tarballs from the individual project websites

2016-10-12 Thread Leo Famulari
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

Re: Source tarballs from PyPI versus tarballs from the individual project websites

2016-10-12 Thread Ludovic Courtès
Christopher Allan Webber skribis: > 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? ‘guix refresh’ works for PyPI but not for arbitrary sites. That would be

Re: Source tarballs from PyPI versus tarballs from the individual project websites

2016-10-12 Thread Christopher Allan Webber
Arun Isaac writes: > 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:

Re: Source tarballs from PyPI versus tarballs from the individual project websites

2016-10-12 Thread Alex Kost
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 > ta

Source tarballs from PyPI versus tarballs from the individual project websites

2016-10-11 Thread Arun Isaac
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/sourc