From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
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:15:34 +0200 [thread overview]
Message-ID: <idjeg6ovcmx.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <20160720092637.5813b122@scratchpost.org>
Danny Milosavljevic <dannym@scratchpost.org> writes:
> Hi Leo,
>
> On Tue, 19 Jul 2016 23:58:23 -0400
> Leo Famulari <leo@famulari.name> wrote:
>
>> In this case, it looks like the Python 2 variant of the package is the
>> same as the Python 3 variant, aside from the Python version. So, you
>> should be able to drop the (properties `((python2-variant ...) line from
>> the python-ptpython package.
>
> 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
What you wrote there is the old way of asking Guix to install a
particular *version* of a package. This has been changed to “@” some
time ago.
This means that you are asking Guix to install a package named
“ptpython” with package version “2” (not Python version 2), but no such
package exists — you only defined two variants of a package with version
0.34.
Our policy with Python *modules* is to prefix them with “python-” or
“python2-”. When you define the Python 3 variant as “python-ptpython”
and give it the name “python-ptpython” then “package-with-python2” will
take care of renaming this to “python2-ptpython” for the Python 2
variant.
(For packages that only provide executables we usually don’t add the
prefix.)
> Now, the ptpython executables are still called the same - so you can't
> install ptpython and ptpython-2 at the same time.
Ah, an executable. If this is not to be used as a library/module does
it even make sense to build it with different versions of Python? If
all you care about is the executables then having a variant with only
the latest version of Python seems sufficient. (We do the same for
snakemake, for example.)
~~ Ricardo
next prev parent reply other threads:[~2016-07-20 10:15 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 ` Ricardo Wurmus [this message]
2016-07-20 21:10 ` Danny Milosavljevic
2016-07-20 10:17 ` Question about (properties `((python2-variant . , (delay " Ludovic Courtès
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=idjeg6ovcmx.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--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).