From: Mathieu Othacehe <othacehe@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: Towards a graphical installer?
Date: Wed, 13 May 2020 09:11:58 +0200 [thread overview]
Message-ID: <87tv0k48ch.fsf@gnu.org> (raw)
In-Reply-To: <87sgg6a2bh.fsf@nckx> (Tobias Geerinckx-Rice's message of "Mon, 11 May 2020 18:01:06 +0200")
Hello Tobias and Jonathan,
> Are you, for example, able to connect to a Wi-Fi network the Gnome way (not
> using the installer), without a Gnome authentication dialogue popping up that
> doesn't understand the notion of ‘no password’? I had to open a terminal and
> ‘passwd’ myself out of that to continue.
No, I kept connman as the installer network-manager.
> Last time I brought this up someone mentioned using Calamares[0]. Not that I
> think that's a good idea, but it's another data point for discussion :-p
My main concern with Calamares, Anaconda & friends is that we will
inevitably have to write some Python/C++ to adapt it to Guix System
installation. Now that we have Guile code covering the whole
installation and associated automated tests, I would prefer not to use
those external tools.
> As much as I dislike Gnome, I think we should first try to use the (most
> likely) default desktop during the installation, and I do think that's
> currently Gnome.
I agree that even though GNOME is heavy and hard to configure, its also
probably to most popular DE.
To adapt the current installer to GNOME, we would need to:
* Switch from connman to NetworkManager.
* Add DBus bindings to control NetworkManager.
* Use 'setxkbmap' or a GNOME API to handle keyboard layout switching.
* Open the info page somewhere else than on TTY2, maybe in a
Web-browser.
Thanks,
Mathieu
next prev parent reply other threads:[~2020-05-13 12:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 13:27 Towards a graphical installer? Mathieu Othacehe
2020-05-11 15:17 ` Jonathan Brielmaier
2020-05-11 16:01 ` Tobias Geerinckx-Rice
2020-05-13 7:11 ` Mathieu Othacehe [this message]
2020-05-11 16:29 ` pelzflorian (Florian Pelz)
2020-05-12 2:58 ` raingloom
2020-05-12 3:49 ` John Soo
2020-05-13 7:20 ` Mathieu Othacehe
2020-05-13 9:28 ` pelzflorian (Florian Pelz)
2020-05-24 20:17 ` Ludovic Courtès
2020-05-11 19:50 ` Pierre Neidhardt
2020-05-11 20:03 ` Leo Famulari
2020-05-11 22:27 ` Christopher Lemmer Webber
2020-05-12 7:09 ` Pierre Neidhardt
2020-05-12 15:33 ` Christopher Lemmer Webber
2020-05-13 5:44 ` dftxbs3e
2020-05-13 7:56 ` Pierre Neidhardt
2020-05-12 6:10 ` dftxbs3e
2020-05-12 6:13 ` dftxbs3e
2020-05-12 20:53 ` hamzeh
2020-05-14 8:08 ` Christopher Baines
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=87tv0k48ch.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).