From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: "Josselin Poiret" <dev@jpoiret.xyz>,
"Andreas Enge" <andreas@enge.fr>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: 63050@debbugs.gnu.org
Subject: bug#63050: "guix pull" requires graphical libraries
Date: Wed, 26 Apr 2023 18:59:44 +0200 [thread overview]
Message-ID: <e97944559fd9661c56dd88131cbd49c5ec8228ec.camel@gmail.com> (raw)
In-Reply-To: <87mt2vc9qp.fsf@jpoiret.xyz>
Hi folks, just dropping by real quick
Am Mittwoch, dem 26.04.2023 um 10:45 +0200 schrieb Josselin Poiret:
> No, guix graph uses its own graphviz implementation! It is used to
> generated png files from .dot files while building the documentation.
>
> I don't really know if we can skip graphical libraries for this
> reason.
Having built glib from scratch more often than is fun, I am quite
certain that the package pulling in our graphics stack is texinfo with
its reference to texlive.
Cheers
next prev parent reply other threads:[~2023-04-26 17:00 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 [this message]
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 ` 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=e97944559fd9661c56dd88131cbd49c5ec8228ec.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=63050@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=dev@jpoiret.xyz \
--cc=ludo@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).