From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>, <rprior@protonmail.com>
Subject: Guix as a system vs as an end-user dev tool (re: Building a software toolchain that works)
Date: Sat, 19 Mar 2022 14:21:07 +0100 [thread overview]
Message-ID: <86cziidqnw.fsf@gmail.com> (raw)
In-Reply-To: <BJz4w-Dvq4U6hET3MMciG3iE_J_W9Af-JDz54zawfcu2lDSfqodxURmyFJ8cMBN-7_MCTo5lxFXQV_GeewbHMLU5HQmpqEw9m7ad4SFA43I=@protonmail.com>
Hi,
> Technically, I think we could use a similar approach to the Docker for
> Desktop system: a "Guix for Desktop" installs software to create and
> manage a minimal Guix System virtual machine which automatically updates
> and reconfigures itself, requiring no manual administration by the
> end-user. And it would install a Guix client that connects to the Guix
> daemon running in the VM using a shared socket, enabling users to
> incorporate Guix transparently into their workflows.
Today, Guix provides a script that allows to install on any foreign
Linux distribution. Somehow, it is already “Guix for Desktop”, no? ;-)
Guix provides a “nightly“ VM. And, IIRC, Guix is also available via
upstream Gnome boxes. Somehow, it is already “Guix for Desktop”, no? ;-)
What do you have in mind for smoothing the workflow of end-user running
Guix? I agree that things are lacking for more adoption but I miss what
you would have in mind with “Guix for Desktop”.
Could you elaborate?
Cheers,
simon
next prev parent reply other threads:[~2022-03-19 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 0:20 Guix as a system vs as an end-user dev tool (re: Building a software toolchain that works) Ryan Prior
2022-03-19 9:06 ` Liliana Marie Prikler
2022-03-19 10:27 ` Jonathan McHugh
2022-03-19 13:21 ` zimoun [this message]
2022-03-19 18:18 ` Ryan Prior
2022-03-19 22:57 ` Yasuaki Kudo
2022-03-21 10:26 ` zimoun
2022-03-20 8:04 ` Zhu Zihao
2022-03-20 10:47 ` Josselin Poiret
2022-03-20 15:15 ` Aurora
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=86cziidqnw.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rprior@protonmail.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).