unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, John Darrington <john@darrington.wattle.id.au>
Subject: Re: Graphical Installer - Call for Testing.
Date: Wed, 12 Jul 2017 13:30:54 +0200	[thread overview]
Message-ID: <20170712133054.3af3ab2d@scratchpost.org> (raw)
In-Reply-To: <87inj4bhqt.fsf@gnu.org>

Hi Ludo,

> Yes.  At the REPL, you can do:
> 
>   ,use(guix)
>   ,run-in-store (system-disk-image installation-os)

I tried:

,use (gnu system vm)
,use (gnu system install)
,use (guix)
,run-in-store (system-disk-image installation-os)
(derivation->output-path $3)

and get

$3 = #<derivation /gnu/store/wqba6wghk3j9jk1sxqb4a2lv730jpcmp-disk-image.drv => /gnu/store/pjrkpnz4bgpiqgdix8ldz0psp53zr4kr-disk-image b0bbe60>
$5 = "/gnu/store/pjrkpnz4bgpiqgdix8ldz0psp53zr4kr-disk-image"

But /gnu/store/pjrkpnz4bgpiqgdix8ldz0psp53zr4kr-disk-image doesn't exist yet.

What should I do to make guix build the image?

Also, what do you think of us providing a "guix system" command for this?

It's kinda difficult to use otherwise...

  reply	other threads:[~2017-07-12 11:31 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04  7:59 Graphical Installer - Call for Testing John Darrington
2017-01-04 13:18 ` Thomas Danckaert
2017-01-04 18:44   ` John Darrington
2017-01-04 15:54 ` dian_cecht
2017-01-04 16:36   ` Ricardo Wurmus
2017-01-04 18:52   ` John Darrington
2017-01-06  3:23 ` Thompson, David
2017-01-07 16:02   ` Christopher Allan Webber
2017-01-06 20:53 ` myglc2
2017-01-06 21:50   ` John Darrington
2017-01-07  2:18     ` myglc2
2017-01-07  4:55       ` myglc2
2017-01-07 20:35         ` Alex Kost
2017-01-07  8:05       ` John Darrington
2017-01-08 18:47       ` Taylan Ulrich Bayırlı/Kammer
2017-01-08 19:28         ` John Darrington
2017-01-08 22:34 ` Ludovic Courtès
2017-01-09 12:31   ` John Darrington
2017-01-10  8:39     ` Ludovic Courtès
2017-01-10 11:57       ` John Darrington
2017-01-13  5:40 ` Chris Marusich
2017-01-13  6:35   ` John Darrington
2017-01-13  7:03     ` Chris Marusich
2017-01-14 13:24       ` David Craven
2017-01-22 14:41         ` John Darrington
2017-01-15  4:06     ` Chris Marusich
2017-01-15  6:55       ` John Darrington
2017-01-15  9:20         ` Chris Marusich
2017-01-15 11:56           ` John Darrington
2017-01-16  9:34             ` Ludovic Courtès
2017-01-16 12:35               ` John Darrington
2017-01-16 17:18           ` John Darrington
2017-01-18  9:36             ` Chris Marusich
2017-07-05 17:27       ` Danny Milosavljevic
2017-07-07  4:48         ` Chris Marusich
2017-07-07  6:13           ` Danny Milosavljevic
2017-07-07 11:37             ` Ludovic Courtès
2017-07-12 11:30               ` Danny Milosavljevic [this message]
2017-07-12 17:31                 ` Danny Milosavljevic
2017-07-17 13:34                 ` 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=20170712133054.3af3ab2d@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=john@darrington.wattle.id.au \
    --cc=ludo@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).