public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] New pre-GLEP: TEST_SUITE_PRESENT variable
Date: Mon, 20 Feb 2023 09:37:16 +0100	[thread overview]
Message-ID: <62060aa8-a618-28e9-ab4f-4e72bed381a8@gentoo.org> (raw)
In-Reply-To: <20230219173211.183497-1-mgorny@gentoo.org>

On 19/02/2023 18.32, Michał Górny wrote:
> +Abstract
> +========
> +
> +A new ``TEST_SUITE_PRESENT`` variable is introduced to indicate whether
> +the package features a test suite.
I wonder if we could not simply use IUSE="test" for this purpose? That 
is, allow declaring the 'test' use flag, even though it is not used in a 
USE conditional, to indicate that the package has a test suite.

With that said, I don't have any strong objections against this 
proposal. But I'd like to mention that with RESTRICT="test", IUSE="test" 
and then TEST_SUITE_PRESENT="true", we end up with an awful lot of test 
related metadata and complexity, which potentially contributes to confusion.

- Flow


  parent reply	other threads:[~2023-02-20  8:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-19 17:32 [gentoo-dev] [PATCH] New pre-GLEP: TEST_SUITE_PRESENT variable Michał Górny
2023-02-19 17:35 ` Anna (cybertailor) Vyalkova
2023-02-19 17:37   ` Michał Górny
2023-02-19 18:09 ` Arsen Arsenović
2023-02-19 19:53 ` Alec Warner
2023-02-19 23:10 ` Maciej Barć
2023-02-20  5:08   ` Michał Górny
2023-02-20 15:04   ` Alec Warner
2023-02-20  8:37 ` Florian Schmaus [this message]
2023-02-20 10:07   ` Sam James
2023-02-20 11:42 ` Ulrich Mueller
2023-02-20 14:40   ` Michał Górny
2023-02-24 13:28 ` Michał Górny

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=62060aa8-a618-28e9-ab4f-4e72bed381a8@gentoo.org \
    --to=flow@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox