From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "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 10:45:34 +0200 [thread overview]
Message-ID: <87mt2vc9qp.fsf@jpoiret.xyz> (raw)
In-Reply-To: <ZEjSp8HrY6SyndaH@jurong>
[-- Attachment #1: Type: text/plain, Size: 3065 bytes --]
Hi Andreas,
Andreas Enge <andreas@enge.fr> writes:
> So "guix pull" builds what is defined as the guix package, but with the
> current checkout as source?
No, guix pull uses (guix self), and the dependencies there are not used
in a singular place like (inputs ...) or (native-inputs ...), but are
peppered throughout the file. However, it uses a reduced dictionary for
specification->package to speed it up, and so gives a pretty good idea
of what's used:
--8<---------------cut here---------------start------------->8---
(("guile" . ,(ref 'guile 'guile-3.0-latest))
("guile-avahi" . ,(ref 'guile-xyz 'guile-avahi))
("guile-json" . ,(ref 'guile 'guile-json-4))
("guile-ssh" . ,(ref 'ssh 'guile-ssh))
("guile-git" . ,(ref 'guile 'guile-git))
("guile-semver" . ,(ref 'guile-xyz 'guile-semver))
("guile-lib" . ,(ref 'guile-xyz 'guile-lib))
("guile-sqlite3" . ,(ref 'guile 'guile-sqlite3))
("guile-zlib" . ,(ref 'guile 'guile-zlib))
("guile-lzlib" . ,(ref 'guile 'guile-lzlib))
("guile-zstd" . ,(ref 'guile 'guile-zstd))
("guile-gcrypt" . ,(ref 'gnupg 'guile-gcrypt))
("guile-gnutls" . ,(ref 'tls 'guile-gnutls))
("guix-daemon" . ,(ref 'package-management 'guix-daemon))
("disarchive" . ,(ref 'backup 'disarchive))
("guile-lzma" . ,(ref 'guile 'guile-lzma))
("gzip" . ,(ref 'compression 'gzip))
("bzip2" . ,(ref 'compression 'bzip2))
("xz" . ,(ref 'compression 'xz))
("po4a" . ,(ref 'gettext 'po4a))
("gettext-minimal" . ,(ref 'gettext 'gettext-minimal))
("gcc-toolchain" . ,(ref 'commencement 'gcc-toolchain))
("glibc-utf8-locales" . ,(ref 'base 'glibc-utf8-locales))
("graphviz" . ,(ref 'graphviz 'graphviz))
("texinfo" . ,(ref 'texinfo 'texinfo)))
--8<---------------cut here---------------end--------------->8---
> The package definition of guix has this among the native inputs:
> ;; XXX: Keep the development inputs here even though
> ;; they're unnecessary, just so that 'guix environment
> ;; guix' always contains them.
> ("autoconf" ,autoconf)
> ("automake" ,automake)
> ("gettext" ,gettext-minimal)
> ("texinfo" ,texinfo)
> ("graphviz" ,graphviz)
> ("help2man" ,help2man)
> ("po4a" ,po4a)))
>
> Maybe these could be dropped then, and we could have an expanded package
> guix-devel that would add these inputs for "guix shell -D guix-devel"?
>
> Or is it needed for "guix graph"?
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.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-04-26 8:46 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 [this message]
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 ` 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=87mt2vc9qp.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--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).