crate importer removes test dependencies for non-top-level crates

  • Open
  • quality assurance status badge
Details
One participant
  • Maxime Devos
Owner
unassigned
Submitted by
Maxime Devos
Severity
normal
M
M
Maxime Devos wrote on 19 Jun 2022 10:56
(address . bug-guix@gnu.org)
c35fa7e5e15d87b4f09efb906c2900f5431c41c3.camel@telenet.be
Hi,

The crate importer removes #:dev-dependencies (i.e., test dependencies
and for benchmarks) for non-top-level crates, presumably because they
aren't used anyway by cargo-build-system because of the #:skip-build?.

However, antioxidant implements build results reuse, and I intend to
implement running tests as well (not yet implemented) (except for when
it would cause cycles), for which these #:dev-dependencies are actually
needed.

Proposal: don't remove the dev-dependencies in (guix import crate).

Greetings,
Maxime.
-----BEGIN PGP SIGNATURE-----

iI0EABYKADUWIQTB8z7iDFKP233XAR9J4+4iGRcl7gUCYq7kxRccbWF4aW1lZGV2
b3NAdGVsZW5ldC5iZQAKCRBJ4+4iGRcl7u35AP4rOJf8AXMVFgsniapRZa4hi13Z
1IPm+gia3kF/PFvG3AD7BLZYu9K8ipLPF8IDDvMnJN6gl0FCukhn431h7UYurwU=
=wbX2
-----END PGP SIGNATURE-----


?