unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Felix Lechner <felix.lechner@lease-up.com>
Cc: guix-devel@gnu.org
Subject: Re: Separating test inputs?
Date: Tue, 02 Jan 2024 08:40:26 +0100	[thread overview]
Message-ID: <87il4cji3h.fsf@elephly.net> (raw)
In-Reply-To: <87o7e42te8.fsf@lease-up.com>


Felix Lechner via "Development of GNU Guix and the GNU System distribution." <guix-devel@gnu.org> writes:

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

Native inputs are those that in the context of cross-building need to
run on the host, not the target.  This is not just for test inputs.

Note also that the presence of test inputs has an impact on the build
itself, such as the configure step, the number of build phases, and even
the output.  In short: without tests this would be a different
derivation.  That’s what we do with the “--without-tests”
transformation: we generate new derivations where tests are not run.

We probably could enhance “--without-tests” to also remove some inputs.

-- 
Ricardo


  reply	other threads:[~2024-01-02  7:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-02  5:31 Separating test inputs? Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-02  7:40 ` Ricardo Wurmus [this message]
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=87il4cji3h.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    /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).