From: Danny Milosavljevic <dannym@scratchpost.org>
To: Rene <ikhuuma@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: create a symlink
Date: Fri, 8 Mar 2019 09:15:32 +0100 [thread overview]
Message-ID: <20190308091532.48fbf293@scratchpost.org> (raw)
In-Reply-To: <cucef7iqqqh.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 886 bytes --]
Hi Rene,
+++ b/guix/scripts/system.scm
@@ -1151,3 +1151,5 @@ argument list and OPTS is the option alist."
;;; End:
;;; system.scm ends here
+
+(install-hurd #$hurd)
That is not going to work there.
#$ unquotes from a build-side g-expression (similar to what "," would do in a quasiquote).
You are not in a g-expression at the position above.
In order to enter the g-expression environment, you could use #~ .
That would give you a lowerable object which someone has to lower in order
to get a derivation for it. Then someone has to do derivation->output-path
in order to get an output path for that derivation.
Or put it into an existing block with #~ .
In your case, I would put the (install-hurd #$hurd) into a bootloader
module, I guess (inside "installer" there--which has a #~ ).
What is supposed to load the "/hurd" that would be created ?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-03-08 8:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 2:54 create a symlink Rene
2018-04-19 6:26 ` Danny Milosavljevic
2018-04-19 21:23 ` Joshua Branson
2018-04-21 14:31 ` Rene
2018-04-27 5:20 ` Rene
2018-04-27 15:08 ` Danny Milosavljevic
2019-03-07 22:11 ` Rene
2019-03-08 8:15 ` Danny Milosavljevic [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-08 21:13 Rene
2019-03-09 8:22 ` Danny Milosavljevic
2019-03-12 20:57 Rene
2019-03-13 11:25 ` Danny Milosavljevic
2019-03-13 14:52 ` Ludovic Courtès
2019-03-25 23:06 ` Danny Milosavljevic
2019-03-28 1:54 Rene
2019-04-03 7:12 ` Chris Marusich
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190308091532.48fbf293@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=ikhuuma@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.