all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Do we really need our own installer?
Date: Thu, 21 Sep 2017 16:17:24 +0200	[thread overview]
Message-ID: <87fubg2l1n.fsf@elephly.net> (raw)
In-Reply-To: <9a7b0563-806c-fb95-f110-16ab42e2bff7@crazy-compilers.com>


Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

> But do we really need our own installer? Why can't we "just" adopt an
> existing one to our needs? Does the installer need to be part of the
> "guix system" command?

The reason why we have a draft curses installer is because John actually
wrote it.  We may be able to adopt an existing graphical installer, but
to my knowledge nobody has investigated this closely enough yet.

The curses installer currently is the closest we have to an installer.
If you feel motivated to take on the work to explore existing GUI
installers, do not let us stop you :)

Originally, we wanted to have an installer that does not hide the Scheme
configuration and lets users play with it.  We wanted to have something
that is a step up from manually following the steps outlined in the
manual.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2017-09-21 14:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 16:05 Do we really need our own installer? Hartmut Goebel
2017-09-21 14:17 ` Ricardo Wurmus [this message]
2017-09-22 14:26 ` Ludovic Courtès
2017-09-25  9:56   ` Hartmut Goebel
2017-09-25 14:35     ` Ricardo Wurmus
2017-10-04 10:08       ` Hartmut Goebel
2017-10-04 15:09       ` GuixSD on PXE (was: Do we really need our own installer?) Adonay Felipe Nogueira

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=87fubg2l1n.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=h.goebel@crazy-compilers.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.