From: "Ludovic Courtès" <ludo@gnu.org>
To: Andreas Enge <andreas@enge.fr>
Cc: 63050@debbugs.gnu.org, Simon Tournier <zimon.toutoune@gmail.com>
Subject: bug#63050: "guix pull" requires graphical libraries
Date: Sat, 20 May 2023 18:12:47 +0200 [thread overview]
Message-ID: <87fs7rvv5s.fsf_-_@gnu.org> (raw)
In-Reply-To: <874jot19fd.fsf_-_@gnu.org> ("Ludovic Courtès"'s message of "Wed, 03 May 2023 21:50:30 +0200")
Hi!
Ludovic Courtès <ludo@gnu.org> skribis:
> We can get an X11-free Graphviz like so:
>
> diff --git a/gnu/packages/graphviz.scm b/gnu/packages/graphviz.scm
> index 26ee96afd4..3a5d33e662 100644
> --- a/gnu/packages/graphviz.scm
> +++ b/gnu/packages/graphviz.scm
> @@ -94,16 +94,12 @@ (define-public graphviz
> (string-append extdir
> "/libgv_guile.so"))))))))
> (inputs
> - (list libxrender
> - libx11
> - gts
> + (list gts
> gd
> guile-3.0 ;Guile bindings
> - pango
> fontconfig
> freetype
> libltdl
> - libxaw
> expat
> libjpeg-turbo
> libpng))
>
>
> The closure size reduction is substantial:
>
> $ ./pre-inst-env guix size graphviz | tail -1
> total: 183.6 MiB
> $ guix size graphviz | tail -1
> total: 242.3 MiB
>
> But I suspect we’d still need the full-blown variant for things like
> xdot.
Here’s a proposal:
https://issues.guix.gnu.org/63610
Ludo’.
next prev parent reply other threads:[~2023-05-20 16:13 UTC|newest]
Thread overview: 30+ 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
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 ` Ludovic Courtès [this message]
2023-05-20 16:38 ` bug#63050: "guix pull" requires graphical libraries Andreas Enge
2023-05-24 13:10 ` Ludovic Courtès
2023-05-25 18:24 ` How many bytes do we add (closure of guix) when adding one new package? Simon Tournier
2023-05-26 16:21 ` Ludovic Courtès
2023-05-30 12:10 ` Simon Tournier
2023-05-30 19:10 ` Csepp
2023-05-31 8:05 ` Faster “guix search” (was Re: How many bytes do we add (closure of guix) when adding one new package?) Simon Tournier
2023-05-31 11:10 ` Csepp
2023-05-31 11:55 ` Attila Lendvai
2023-05-30 20:55 ` How many bytes do we add (closure of guix) when adding one new package? Jack Hill
2023-05-31 8:27 ` Simon Tournier
2023-05-31 12:47 ` Guillaume Le Vaillant
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fs7rvv5s.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=63050@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=zimon.toutoune@gmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.