From: ludo@gnu.org (Ludovic Courtès)
To: Nikita Karetnikov <nikita@karetnikov.org>
Cc: guix-devel@gnu.org
Subject: Re: Some thoughts on installers
Date: Tue, 17 Sep 2013 13:52:29 +0200 [thread overview]
Message-ID: <87fvt3fywy.fsf@gnu.org> (raw)
In-Reply-To: <87eh8nyh6w.fsf@karetnikov.org> (Nikita Karetnikov's message of "Tue, 17 Sep 2013 12:40:23 +0400")
Nikita Karetnikov <nikita@karetnikov.org> skribis:
> I haven’t seen an installer that isn’t organized in a step-by-step
> fashion. A user is forced to press the “Next” button every 5 minutes or
> so. It’s impossible to do anything else because that will increase the
> installation time. So the user has to sit in front of the computer for
> 40 minutes and wait for the button to become active.
>
> I assume that installers are written in such a way because it’s easier
> for developers. Let’s not repeat this mistake when we write our own.
> Instead, I propose to get the needed information beforehand (on the
> first screen). Then it’d be only necessary to press “Install.” A user
> could check the progress bar and be free to do something else.
The idea is to start with NixOS-style declarative configuration. You
provide a configuration file that defines the structure of the system to
be installed (or you generate that file via a M-x customize kind of user
interface, say), and then run the install process, which instantiates
the whole thing non-interactively.
Ludo’.
prev parent reply other threads:[~2013-09-17 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 8:40 Some thoughts on installers Nikita Karetnikov
2013-09-17 11:52 ` Ludovic Courtès [this message]
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=87fvt3fywy.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=nikita@karetnikov.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).