From: ludo@gnu.org (Ludovic Courtès)
To: Zachary Kanfer <zkanfer@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: How do I make a manifest file that installs a specific version of a dependency?
Date: Sun, 12 Mar 2017 22:50:37 +0100 [thread overview]
Message-ID: <87shmi17wy.fsf@gnu.org> (raw)
In-Reply-To: <CAFXT+ROh_LJL=avnMKvxdDxu1u7h67_hFiaaHA2DMu_8pZe4BA@mail.gmail.com> (Zachary Kanfer's message of "Sun, 12 Mar 2017 00:55:01 -0500")
Hello,
Zachary Kanfer <zkanfer@gmail.com> skribis:
> Running `guix package -m` on a file with this line `(list icedtea-2.6
> "jdk")` gives an error "In procedure module-lookup: Unbound variable:
> icedtea-2.6".
>
> I get the same error for the following lines:
>
> `(list icedtea-2.6.6 "jdk")`
> `(list icedtea@2.6.6 "jdk")`
>
> `guix package -s icedtea` reports that there is a version 2.6.6. How do I
> specify this in a manifest file? Thanks.
You should use ‘specification->package’ as discussed at
<https://www.gnu.org/software/guix/manual/html_node/Using-the-Configuration-System.html#index-specification_002d_003epackage>.
The ‘specification->package’ procedure takes a spec like those you’d
write on the ‘guix package -i’ command line, and returns the
corresponding package. ‘specification->package+output’ works similarly
but also returns the specified output (the part that comes after the
colon).
So your manifest would look something like:
(use-modules (gnu))
(packages->manifest
(map (compose list specification->package+output)
'("icedtea@2.6.6:jdk" "emacs" "vim" …)))
HTH!
Ludo’.
next prev parent reply other threads:[~2017-03-12 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 5:55 How do I make a manifest file that installs a specific version of a dependency? Zachary Kanfer
2017-03-12 21:50 ` Ludovic Courtès [this message]
2017-03-12 23:50 ` Zachary Kanfer
2017-03-13 8:24 ` Ludovic Courtès
2017-03-13 8:17 ` Chris Marusich
2017-03-13 9:20 ` Ludovic Courtès
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=87shmi17wy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=help-guix@gnu.org \
--cc=zkanfer@gmail.com \
/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).