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: Mon, 13 Mar 2017 09:24:24 +0100 [thread overview]
Message-ID: <8737eheg93.fsf@gnu.org> (raw)
In-Reply-To: <CAFXT+RMAu9oSXaZOiDf9zeyU72BLkF6Pc61yR+3rRt-GYN_o-w@mail.gmail.com> (Zachary Kanfer's message of "Sun, 12 Mar 2017 19:50:07 -0400")
Hi,
Zachary Kanfer <zkanfer@gmail.com> skribis:
> Thanks for responding. When I run this, I got this error:
>
> Directory
> '/gnu/store/jvj247prbwy1jn20svy4ls5yjscpmiss-xdg-mime-database/share/mime/packages'
> does not exist!
>
> My manifest file only installs racket and icedtea@2.6.6:jdk. If I rerun the
> same command, I get "nothing to be done".
Is this really an error? Does “guix package -I” lists both Racket and
IcedTea as installed?
I suspect this message might be a harmless warning from one of the
profile hooks, but it’s admittedly confusing.
> As a side note, is this the commonly recommended way to structure the
> manifest file? The documentation for `guix package -m` instead says to use
> `use-package-modules`, and doesn't mention anything about
> `specification->package+output`.
The documentation has been updated to suggest that:
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=6cd1059340
(It will show up in the on-line copy when we update it.)
Thanks,
Ludo’.
next prev parent reply other threads:[~2017-03-13 8:24 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
2017-03-12 23:50 ` Zachary Kanfer
2017-03-13 8:24 ` Ludovic Courtès [this message]
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=8737eheg93.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).