From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: guix import error
Date: Fri, 16 Oct 2020 14:25:16 +0200 [thread overview]
Message-ID: <87d01ibbo3.fsf@nckx> (raw)
In-Reply-To: <fb468269-4811-b5ce-8dba-c7dd55ae5393@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
Zelphir,
Zelphir Kaltstahl 写道：
> $ guix import pypi 'jupyterlab@2.1.5' --recursive
It will work if you substitute ‘/’ for ‘@’. Yes, this is a happy
accident specific to the PyPI importer, and I'm sure you can guess
why it happens to work.
>> guix import hackage mtl@2.1.3.1
>
> But that is in the "hackage" import section. Is the same not
> available
> for PyPI?
[...]
> Do the various importers work differently?
Unfortunately so. It would be great(TM) if PACKAGE[@VERSION] were
standard. Each importer could handle it properly (e.g., by
turning it into "/") or return a friendlier ‘the foo importer does
not yet support versions’ error.
I don't have the time, but this sounds like a good
intermediate-level hack for someone who does :-)
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-10-16 12:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 11:50 guix import error Zelphir Kaltstahl
2020-10-16 12:19 ` zimoun
2020-10-16 12:25 ` Tobias Geerinckx-Rice [this message]
2020-10-16 13:51 ` zimoun
2020-10-18 11:55 ` guix import error + New: setting up a jupyterlab environment Zelphir Kaltstahl
2020-10-18 16:35 ` Efraim Flashner
2020-10-19 14:31 ` Zelphir Kaltstahl
2020-10-19 16:54 ` Efraim Flashner
2020-10-19 18:19 ` Zelphir Kaltstahl
2020-10-19 21:12 ` Zelphir Kaltstahl
2020-10-21 7:18 ` Efraim Flashner
2020-10-24 19:42 ` Zelphir Kaltstahl
2020-10-25 8:52 ` Efraim Flashner
2020-10-25 11:49 ` Zelphir Kaltstahl
2020-10-21 7:09 ` Efraim Flashner
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=87d01ibbo3.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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.
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).