From: "Gábor Boskovits" <boskovits@gmail.com>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Testing the installer
Date: Thu, 23 Jan 2020 12:21:27 +0100 [thread overview]
Message-ID: <CAE4v=pj6R70pvLVPEsVYjJo+sd77bj1QV0=CTHYoBcL=c7VTgw@mail.gmail.com> (raw)
In-Reply-To: <87y2tyfr24.fsf@gmail.com>
Hello Mathieu,
Mathieu Othacehe <m.othacehe@gmail.com> ezt írta (időpont: 2020. jan.
23., Cs, 10:42):
>
>
> Hey!
>
> > I’ve pushed ‘wip-installer-test’, which implements said protocol. See
> > screenshot below! :-)
>
> Woow, that's impressive :)
>
> I just gave you access to Guile-newt repository so that you can
> integrate your changes. I will create a new release once its done.
>
> In the future, I would have liked to keep open the possibility of having
> one installer with multiple graphical backends (newt, gtk, cli). That
> would mean that we would need to factorize the protocol part in the
> backend agnostic part of the installer.
>
> Anyway, for now it would be completely over-engineered, as we don't know
> yet if a new backend will come one day.
This is a bit off topic, but I am about to create an automatic
installer, that is
a candidate for a new backend. It currently works by providing a configuration
record, and then executes a few things from the installer.
(It does a lookup for a candidate installation target disk, autopartitions it,
then injects the bootloader and file-system fields into an operating-system
template, and finally does a system installation.)
I will have a look at the new protocol soon, to see if this project
can benefit from that.
>
> Please let me know if you want help on some point but, I think that I'll
> try to tackle the "installer cannot restart issue".
>
> Thanks,
>
> Mathieu
>
Best regards,
g_bor
--
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21
next prev parent reply other threads:[~2020-01-23 11:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 22:13 Testing the installer Ludovic Courtès
2020-01-12 23:34 ` sirgazil
2020-01-20 17:49 ` sirgazil
2020-01-14 8:02 ` Mathieu Othacehe
2020-01-22 22:27 ` Ludovic Courtès
2020-01-23 9:41 ` Mathieu Othacehe
2020-01-23 11:21 ` Gábor Boskovits [this message]
2020-01-23 23:07 ` Bengt Richter
2020-01-24 7:48 ` Gábor Boskovits
2020-01-24 9:23 ` Ludovic Courtès
2020-01-23 14:54 ` Ludovic Courtès
2020-01-20 11:47 ` Jonathan Brielmaier
-- strict thread matches above, loose matches on Subject: below --
2018-06-13 3:57 swedebugia
2018-06-13 19:47 ` Ricardo Wurmus
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='CAE4v=pj6R70pvLVPEsVYjJo+sd77bj1QV0=CTHYoBcL=c7VTgw@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 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).