From: "Ludovic Courtès" <ludo@gnu.org>
To: Adam Faiz <adam.faiz@disroot.org>
Cc: guix-devel@gnu.org, dannym@scratchpost.org
Subject: Re: GUI for Guix
Date: Wed, 04 Oct 2023 17:52:09 +0200 [thread overview]
Message-ID: <875y3mcrme.fsf@gnu.org> (raw)
In-Reply-To: <adafe991-c156-2ced-b750-d3b26a2a2303@disroot.org> (Adam Faiz's message of "Sun, 1 Oct 2023 00:07:44 +0800")
Hi,
Adam Faiz <adam.faiz@disroot.org> skribis:
> There are currently 4(maybe more?) different approaches for a Guix GUI:
> 1. Guix backend for PackageKit (https://issues.guix.gnu.org/17152)
> 2. A GTK program written by Danny Milosavljevic in Guile (https://gitlab.com/daym/guix-gui/)
> 3. A Qt program written for a non-FSDG distro downstream of Guix System (https://git.pantherx.org/development/applications/px-software)
> 4. Emacs-Guix, currently broken (https://issues.guix.gnu.org/55013)
>
> Which of these should be worked on? I tried packaging guix-gui, but it doesn't work without the workaround mentioned in the README.
> I think packaging it should wait until the guile-gi bug[1] is fixed.
>
> [1]: https://github.com/spk121/guile-gi/issues/96
FWIW I would suggest prioritizing #2 as it seems to be a low-hanging
fruit (what’s up with this Guile-GI bug though?).
Longer-term, #1 may be more fruitful, although one drawback is that
PackageKit/GNOME Software may be biased towards system-wide,
root-restricted installations.
Ludo’.
next prev parent reply other threads:[~2023-10-04 15:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 16:07 GUI for Guix Adam Faiz
2023-09-30 17:08 ` jbranso
2023-10-02 18:52 ` Thompson, David
2023-10-01 20:52 ` Ricardo Wurmus
2023-10-02 20:25 ` Suhail Singh
2023-10-04 15:49 ` Ludovic Courtès
2023-10-06 2:58 ` Suhail Singh
2023-10-04 15:52 ` Ludovic Courtès [this message]
2023-10-14 15:59 ` Maxim Cournoyer
-- strict thread matches above, loose matches on Subject: below --
2023-10-02 8:53 Adam Faiz
2023-10-02 15:08 ` Ricardo Wurmus
2023-10-03 9:00 ` Daniel Meißner
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=875y3mcrme.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=adam.faiz@disroot.org \
--cc=dannym@scratchpost.org \
--cc=guix-devel@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).