From: Jan Nieuwenhuizen <janneke@gnu.org>
To: 32749@debbugs.gnu.org
Subject: bug#32749: package-with-explicit-inputs leaks-in additional inputs
Date: Mon, 17 Sep 2018 17:59:54 +0200 [thread overview]
Message-ID: <87lg803yit.fsf@gnu.org> (raw)
In-Reply-To: <87tvmo4f1d.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Mon, 17 Sep 2018 12:03:10 +0200")
Jan Nieuwenhuizen writes:
> Should `package-with-explicit-inputs' behave like I think it does, i.e.,
> should both test packages list the same dependencies, or am I missing
> something?
Printing the packages in the Guix Repl gives this result
--8<---------------cut here---------------start------------->8---
(package-inputs gnu-make-no-implicit-inputs)
$12 = (("libc" #<package glibc-bootstrap@0 gnu/packages/bootstrap.scm:150 3f39cc0>) ("gcc" #<package gcc-bootstrap@0 gnu/packages/bootstrap.scm:150 3f39c00>) ("binutils" #<package binutils-bootstrap@0 gnu/packages/bootstrap.scm:150 3f39b40>) ("coreutils&co" #<package bootstrap-binaries@0 gnu/packages/bootstrap.scm:150 3f39a80>) ("bash" #<package bootstrap-binaries@0 gnu/packages/bootstrap.scm:150 3f39a80>))
scheme@(gnu packages pawei)> (map car (package-inputs gnu-make-no-implicit-inputs))
$13 = ("libc" "gcc" "binutils" "coreutils&co" "bash")
scheme@(gnu packages pawei)> (package-native-inputs gnu-make-no-implicit-inputs)
$14 = ()
scheme@(gnu packages pawei)> (package-propagated-inputs gnu-make-no-implicit-inputs)
$15 = ()
scheme@(gnu packages pawei)> (package-inputs gnu-make-explicit-inputs)
$16 = (("libc" #<package glibc-bootstrap@0 gnu/packages/bootstrap.scm:150 3f39cc0>) ("gcc" #<package gcc-bootstrap@0 gnu/packages/bootstrap.scm:150 3f39c00>) ("binutils" #<package binutils-bootstrap@0 gnu/packages/bootstrap.scm:150 3f39b40>) ("coreutils&co" #<package bootstrap-binaries@0 gnu/packages/bootstrap.scm:150 3f39a80>) ("bash" #<package bootstrap-binaries@0 gnu/packages/bootstrap.scm:150 3f39a80>) ("guile" #<package guile@2.0.14 gnu/packages/bootstrap.scm:150 3f39900>))
scheme@(gnu packages pawei)>
$17 = (("pkg-config" #<package pkg-config@0.29.2 gnu/packages/bootstrap.scm:150 3f39780>))
scheme@(gnu packages pawei)> (package-propagated-inputs gnu-make-explicit-inputs)
$18 = ()
scheme@(gnu packages pawei)> (package-native-inputs gnu-make-explicit-inputs)
$19 = (("pkg-config" #<package pkg-config@0.29.2 gnu/packages/bootstrap.scm:150 3f39780>))
--8<---------------cut here---------------end--------------->8---
which is exactly what I expect to see when I read the Guile code for the
package descriptions; but is still a bit surprising to me: where do all
the extra inputs come from in the graph?
janneke
next prev parent reply other threads:[~2018-09-17 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 10:03 bug#32749: package-with-explicit-inputs leaks-in additional inputs Jan Nieuwenhuizen
2018-09-17 15:59 ` Jan Nieuwenhuizen [this message]
2018-09-17 20:26 ` Ludovic Courtès
2018-09-18 4:23 ` Jan Nieuwenhuizen
2018-09-18 14:38 ` Ludovic Courtès
2018-09-18 15:03 ` Jan Nieuwenhuizen
2018-09-19 20:42 ` 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=87lg803yit.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=32749@debbugs.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).