GNU bug report logs - #63050
"guix pull" requires graphical libraries

Previous Next

Full log

View this message in rfc822 format

From: Csepp <raingloom <at> riseup.net>
To: Simon Tournier <zimon.toutoune <at> gmail.com>
Cc: ludo <at> gnu.org, 63050 <at> debbugs.gnu.org, andreas <at> enge.fr
Subject: bug#63050: "guix pull" requires graphical libraries
Date: Fri, 05 May 2023 15:21:16 +0000

Simon Tournier <zimon.toutoune <at> gmail.com> writes:

> Hi,
>
> On Wed, 03 May 2023 at 21:33, Ludovic Courtès <ludo <at> gnu.org> wrote:
>
>>> Why does Guix require ’graphviz’ in the first place?
>>
>> It uses it to build images in the manual.
>
> Ah.  So we are dragging X11 libraries as libx11 for one or two figures
> in the manual. :-)
>
> Although that’s not exactly the same as “guix pull”,
>
>     guix graph guix -t bag-emerged
>
> gives an idea.  Well, for example, there is a path from guix to ninja
> via graphviz.
>
> While I understand that the documentation is important, could we skip it
> for some architectures?

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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.