From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: "Arsen Arsenović" <arsen@gentoo.org>, python@gentoo.org
Subject: Re: [gentoo-dev] Handling installed tests
Date: Fri, 09 Aug 2024 18:12:51 +0200 [thread overview]
Message-ID: <a1113a12d5113f1336543661d3f7f95474b5d705.camel@gentoo.org> (raw)
In-Reply-To: <87ttftr9ay.fsf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
On Fri, 2024-08-09 at 16:43 +0100, Sam James wrote:
> Hi,
>
> I'm currently working on packaging dtrace which doesn't (at least
> currently, may not ever) support running tests as non-root, but
> does support handling installing them for later manual use.
>
> This raises a question: how should we control installing such tests? How
> should the user request that?
>
> USE=test isn't suitable because:
> a) I generally expect it not to mutate the image;
> b) ago, rightly, based on this has a tinderbox check which looks for
> added/removed files when tests are enabled.
>
> I'd like to pick some name which is suitable for us to use elsewhere and
> it's not really a package-specific issue. Thoughts?
>
> Please assume the tests are large enough to justify conditional install
> and have additional dependencies.
>
Sounds a bit related to USE=examples.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2024-08-09 16:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 15:43 [gentoo-dev] Handling installed tests Sam James
2024-08-09 15:55 ` Eli Schwartz
2024-08-09 15:59 ` Maciej Barć
2024-08-09 16:05 ` Eli Schwartz
2024-08-09 16:12 ` Michał Górny [this message]
2024-08-16 5:02 ` Joonas Niilola
2024-08-18 19:06 ` Sam James
2024-08-19 4:59 ` Joonas Niilola
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=a1113a12d5113f1336543661d3f7f95474b5d705.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=arsen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=python@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