> 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?

An additional test-inputs field sounds like a good idea. Maybe the
test-inputs could be made available just for the test phase (I'd assume
this could be implemented with add-test-inputs and remove-test-inputs
phases) so that they would be isolated from other parts of the build
process.