GNU bug report logs -
#40412
cargo-build-system hides the package dependency graph
Previous Next
To reply to this bug, email your comments to 40412 AT debbugs.gnu.org.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#40412
; Package
guix
.
(Fri, 03 Apr 2020 17:45:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Leo Famulari <leo <at> famulari.name>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Fri, 03 Apr 2020 17:45:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Some Guix commands like `guix graph` and `guix show` don't work as
expected for packages using the cargo-build-system.
The cargo-build-system uses only the source code of a package's
dependencies when building.
To achieve this, the build system does not refer to dependencies with
the usual 'inputs', 'native-inputs', and 'propagated-inputs', but
instead with the Scheme keywords #:cargo-inputs and
#:cargo-development-inputs. [0]
This means that it's not possible to work with the package dependency
graph like with other packages.
As a result, some Guix commands don't work as expected, such as `guix
graph` and `guix show`. I wonder if `guix refresh --update` works?
I'm not sure if this can be improved — there is a comment in ((guix
build-system cargo) expand-crate-sources) that explains why we did it
this way and acknowledges the problems.
[0] For example:
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/crates-io.scm?id=e7a353ed468a805af6ad6b06b0dc0909393ff8fa#n89
This bug report was last modified 5 years and 70 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.