From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: Mathieu Othacehe <othacehe@gnu.org>, guix-devel@gnu.org
Subject: Re: Towards a graphical installer?
Date: Mon, 11 May 2020 18:01:06 +0200 [thread overview]
Message-ID: <87sgg6a2bh.fsf@nckx> (raw)
In-Reply-To: <be8e28f0-8c8d-b305-3061-642c2a875945@web.de>
[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]
Mathieu, Jonathan,
A truly graphical installer would be glorious. Exploring it was
what led to the quick & dirty zisofs patch.
Like you I was able to get a surprisingly working Gnome desktop,
but it was very rough at the edges. (However my compressed images
were closer to 1.4 GiB than your 1.7 which might explain that; cut
out things like GDM &c.).
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.
I ran into so many paper cuts like this I burnt out due to Gnome
being, you know, Gnome.
Mathieu Othacehe 写道:
> Now, I'm not sure this is something we want to merge
> as-is. Maybe, it's
> time to port the installer to a GTK3 application, or a Web
> application. As we already have something working, porting (gnu
> installer) to a new graphical backend, could be not so hard.
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
Jonathan Brielmaier 写道:
> Nice initiative! Maybe it would be an idea to use XFCE instead
> of GNOME
> as it's tend to be a little smaller. And maybe more stable as
> they don't
> have that many releases...
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.
Not at all costs of course. Size. Stability. Sanity.
Kind regards,
T G-R
[0]: https://calamares.io/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-05-11 16:07 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 [this message]
2020-05-13 7:11 ` Mathieu Othacehe
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=87sgg6a2bh.fsf@nckx \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=jonathan.brielmaier@web.de \
--cc=othacehe@gnu.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).