all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Installer and luks support.
Date: Sun, 9 Dec 2018 12:25:09 +0100	[thread overview]
Message-ID: <CAE4v=pi_jttMWeiXcD2G1-YkXdx=Kf_LdLWFgdUsMuHN0Er95Q@mail.gmail.com> (raw)
In-Reply-To: <87o99vymr2.fsf@gmail.com>

Mathieu Othacehe <m.othacehe@gmail.com> ezt írta (időpont: 2018. dec.
9., V, 12:15):
>
>
> Hi Gábor,
>
> > Can't we offer here the option to retry the failed step? i.e. guix system init
> > in this case? I mean we have everything set up to simply retry. Does
> > that make sense?
>
> Yes that could be a viable option. We could allow the user to launch
> again the install command, but we cannot allow him to go back to the
> installer menu and resume the process wherever.
>

I believe this might be a good choice first. This seems also easier to do.

> Or, we could keep the menu active but remove some critical steps such as
> "partitioning" that require umounting/closing.
>

On the long run it would be nicer to get the dependencies and the resources
figured out, so the we can go back to whatever step we want. I mean if a step
needs a resource available, for example the mount then we can make it available
when entering that step. And when for example we repartiton the drive, then all
later steps depends on that, so we need to redo all the later steps. WDYT?

> What do you think?
>
> Thanks,
>
> Mathieu

  reply	other threads:[~2018-12-09 11:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-08  1:58 Installer and luks support Mathieu Othacehe
2018-12-08 23:05 ` Ludovic Courtès
2018-12-09  1:15   ` Mathieu Othacehe
2018-12-09 10:47     ` Gábor Boskovits
2018-12-09 11:15       ` Mathieu Othacehe
2018-12-09 11:25         ` Gábor Boskovits [this message]
2018-12-09 13:35     ` Ludovic Courtès
2018-12-09 14:11       ` Mathieu Othacehe

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='CAE4v=pi_jttMWeiXcD2G1-YkXdx=Kf_LdLWFgdUsMuHN0Er95Q@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=m.othacehe@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.