From: Simon Tournier <zimon.toutoune@gmail.com>
To: Csepp <raingloom@riseup.net>
Cc: ludo@gnu.org, 63050@debbugs.gnu.org, andreas@enge.fr
Subject: bug#63050: "guix pull" requires graphical libraries
Date: Tue, 09 May 2023 14:36:28 +0200 [thread overview]
Message-ID: <87v8h165rn.fsf@gmail.com> (raw)
In-Reply-To: <87ttwq952b.fsf@riseup.net>
Hi,
On ven., 05 mai 2023 at 15:21, Csepp <raingloom@riseup.net> wrote:
> Or just move it to a separate output or package? That should really be
> something done for all packages automatically tbh. Alpine gets this right.
Well, I do not think a separate output would be possible and we are not
talking about the package named ’guix’ but about what is implemented by
the module (guix self).
Somehow, I agree that one direction would to make optional some
features. The current proposal for tackling this issue is the reduction
of the closure by removing lix11 and libxrender as discussed in [1].
1: https://issues.guix.gnu.org/msgid/874jot19fd.fsf_-_@gnu.org
Cheers,
simon
next prev parent reply other threads:[~2023-05-09 17:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 10:13 bug#63050: "guix pull" requires graphical libraries Andreas Enge
2023-04-25 21:48 ` Ludovic Courtès
2023-04-26 7:28 ` Andreas Enge
2023-04-26 8:45 ` Josselin Poiret via Bug reports for GNU Guix
2023-04-26 16:59 ` Liliana Marie Prikler
2023-04-26 17:25 ` Andreas Enge
2023-04-26 18:39 ` Josselin Poiret via Bug reports for GNU Guix
2023-04-26 19:21 ` Andreas Enge
2023-04-26 19:34 ` Liliana Marie Prikler
2023-04-28 15:18 ` Simon Tournier
2023-05-03 19:33 ` Ludovic Courtès
2023-05-04 8:56 ` Simon Tournier
2023-05-05 15:21 ` Csepp
2023-05-09 12:36 ` Simon Tournier [this message]
2023-05-11 21:30 ` Csepp
2023-05-03 19:50 ` bug#63050: Reducing the closure size of Graphviz Ludovic Courtès
2023-05-04 9:00 ` Simon Tournier
2023-05-20 16:12 ` bug#63050: "guix pull" requires graphical libraries Ludovic Courtès
2023-05-20 16:38 ` Andreas Enge
2023-05-24 13:10 ` Ludovic Courtès
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=87v8h165rn.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=63050@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=ludo@gnu.org \
--cc=raingloom@riseup.net \
/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).