From: Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org>
To: guix-devel@gnu.org
Subject: Separating test inputs?
Date: Mon, 01 Jan 2024 21:31:27 -0800 [thread overview]
Message-ID: <87o7e42te8.fsf@lease-up.com> (raw)
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
next reply other threads:[~2024-01-02 5:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 5:31 Felix Lechner via Development of GNU Guix and the GNU System distribution. [this message]
2024-01-02 7:40 ` Separating test inputs? Ricardo Wurmus
2024-01-02 8:14 ` Saku Laesvuori
2024-01-02 21:13 ` Liliana Marie Prikler
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=87o7e42te8.fsf@lease-up.com \
--to=guix-devel@gnu.org \
--cc=felix.lechner@lease-up.com \
/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).