Hi Sam,

We have a "source" flag so maybe we could either use that or have 
"test-source" BUT we also have FEATURES="installsources" ...so (if I 
understand that feature correctly) we can just run test from 
/usr/src/debug/${CATEGORY}/${PF}

But IMO I'd rather clone the project and run test from the clone.

Of source the drawback of installsources & git cloning is that emerge 
does not run any modifications on the tests nor applies patches to them 
nor buildsystem/testrunner used.

W dniu 9.08.2024 o 17:43, Sam James pisze:
> 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.)
> 
> thanks,
> sam

-- 
Have a great day!

~ Maciej XGQT Barć

https://wiki.gentoo.org/wiki/User:Xgqt
9B0A 4C5D 02A3 B43C 9D6F D6B1 14D7 4A1F 43A6 AC3C