all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
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 22:15:53 +0200	[thread overview]
Message-ID: <87h98hmih2.fsf@gnu.org> (raw)
In-Reply-To: <cu74m4hzkkk.fsf@systemreboot.net> (Arun Isaac's message of "Wed, 12 Oct 2016 20:22:11 +0530")

Arun Isaac <arunisaac@systemreboot.net> 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’.

  reply	other threads:[~2016-10-12 20:16 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 [this message]
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=87h98hmih2.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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.