Hi, A better test infrastructure in Guix would probably be good, but is not ready yet. Would it make sense, however, to split out those inputs only needed for testing?
Such a step would probably make bootstrapping new architectures a lot easier. It would also reduce the dependency graph in Guix, since tests are not needed to either build or use a package. In Debian, test prerequisites are annotated awkwardly with <!nocheck> in the build prerequisites. (I think Guix calls them native-inputs.) You can see some of Debian's funny notations here [1] and here. [2] This is a proposal for 'test-inputs'. Any thoughts? Kind regards Felix [1] https://tracker.debian.org/media/packages/libm/libmouse-perl/control-2.5.10-1 [2] https://tracker.debian.org/media/packages/l/lintian/control-2.116.3
