From: ludo@gnu.org (Ludovic Courtès)
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: Question about (properties `((python2-variant . , (delay XXX)))) and name resolution
Date: Wed, 20 Jul 2016 12:17:53 +0200 [thread overview]
Message-ID: <87d1m8d35a.fsf@gnu.org> (raw)
In-Reply-To: <20160720092637.5813b122@scratchpost.org> (Danny Milosavljevic's message of "Wed, 20 Jul 2016 09:26:37 +0200")
Danny Milosavljevic <dannym@scratchpost.org> skribis:
> I tried that, but I still can't do
>
> $ guix package -i ptpython-2
>
> because:
>
> guix package: error: ptpython: package not found for version 2
[...]
> (name "ptpython-2"))))
In the former command-line package specification syntax, which is still
supported but deprecated, “ptpython-2” was taken to mean “version 2 of
package ‘ptpython’”. Because of this, you cannot refer to this
“ptpython-2” package from the command-line (except with -e).
The solution is to call it differently, like “ptpython2”.
Eventually (I’d say after 0.10.1 is released) we’ll remove support for
the old syntax and the problem will be gone.
HTH!
Ludo’.
next prev parent reply other threads:[~2016-07-20 10:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 17:47 Question about (properties `((python2-variant . ,(delay XXX)))) and name resolution Danny Milosavljevic
2016-07-20 3:58 ` Question about (properties `((python2-variant . , (delay " Leo Famulari
2016-07-20 7:26 ` Question about (properties `((python2-variant . ,(delay " Danny Milosavljevic
2016-07-20 10:15 ` Question about (properties `((python2-variant . , (delay " Ricardo Wurmus
2016-07-20 21:10 ` Question about (properties `((python2-variant . ,(delay " Danny Milosavljevic
2016-07-20 10:17 ` Ludovic Courtès [this message]
2016-07-22 8:59 ` Installing incompatible major versions of packages alongside each other Danny Milosavljevic
2016-07-22 13:02 ` Ludovic Courtès
2016-07-22 14:14 ` 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
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=87d1m8d35a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=dannym@scratchpost.org \
--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 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).