public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Sam James <sam@gentoo.org>
Cc: "Arsen Arsenović" <arsen@gentoo.org>, python@gentoo.org
Subject: Re: [gentoo-dev] Handling installed tests
Date: Fri, 9 Aug 2024 11:55:25 -0400	[thread overview]
Message-ID: <91a1f789-96a4-42a5-9d27-d02853309a33@gentoo.org> (raw)
In-Reply-To: <87ttftr9ay.fsf@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 1110 bytes --]

On 8/9/24 11:43 AM, 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.
> 
> (This is arguably related to https://bugs.gentoo.org/867799 and so on
> wrt dev-lang/python always installing tests.)


This reminds me of
https://wiki.gnome.org/Initiatives/GnomeGoals/InstalledTests so it's
definitely not a dtrace specific issue.


-- 
Eli Schwartz


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2024-08-09 15:55 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 [this message]
2024-08-09 15:59 ` Maciej Barć
2024-08-09 16:05   ` Eli Schwartz
2024-08-09 16:12 ` Michał Górny
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=91a1f789-96a4-42a5-9d27-d02853309a33@gentoo.org \
    --to=eschwartz@gentoo.org \
    --cc=arsen@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=python@gentoo.org \
    --cc=sam@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