unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 49083@debbugs.gnu.org
Subject: bug#49083: ‘guix import pypi’ fails in the absence of “sdist” releases
Date: Sun, 20 Jun 2021 23:03:36 +0200	[thread overview]
Message-ID: <87o8c08d07.fsf@gnu.org> (raw)
In-Reply-To: <ccf3451dbe51719d00e96027f48aee7729a22fad.camel@student.tugraz.at> (Leo Prikler's message of "Fri, 18 Jun 2021 10:56:33 +0200")

Hi,

Leo Prikler <leo.prikler@student.tugraz.at> skribis:

> Wheels are (as far as I understand) binary distributions, so they ought
> to contain everything, that gets put into site-packages.  I don't think
> they make for good source packages.  In particular, the jaxlib wheel
> contains a bunch of shared objects and almost none of the source that
> one can see on Github.

Uh, worse than I thought.

> Instead of erroring out, we could try to check whether the homepage
> points to a git forge and try to generate a git-reference from that. 

Sounds good.  I suspect special-casing github.com would already catch
most cases…  Problem is that we would not know which tag to use, unless
we go to great lengths to guess that.

> Failing this, we might want to set source to something, that produces
> an error when read or when used as a variable, similar to how unknown
> licenses are handled.

Right; not failing seems preferable.

Thanks,
Ludo’.




  reply	other threads:[~2021-06-20 21:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-18  7:33 bug#49083: ‘guix import pypi’ fails in the absence of “sdist” releases Ludovic Courtès
2021-06-18  8:56 ` Leo Prikler
2021-06-20 21:03   ` Ludovic Courtès [this message]
2021-06-22 18:58     ` Maxim Cournoyer
2022-02-02 17:46       ` Ludovic Courtès
2022-02-02 21:45         ` Maxim Cournoyer

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=87o8c08d07.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=49083@debbugs.gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    /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).