[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Source tarballs from PyPI versus tarballs from the individual projec
From: |
Ludovic Courtès |
Subject: |
Re: Source tarballs from PyPI versus tarballs from the individual project websites |
Date: |
Wed, 12 Oct 2016 22:15:53 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) |
Arun Isaac <address@hidden> 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 equivalent upstream tarball URI and put
> it in the package definition?
The problem is that the PyPI “updater” that ‘guix refresh’ uses needs to
be able to determine that a package is a “PyPI package”, which is what
the ‘pypi-package?’ predicate in (guix import pypi) does. If a package
uses a URL other than pypi.python.org, that predicate returns false.
Ludo’.