On 09/08/2024 18:11, Michał Górny wrote:
On Fri, 2024-08-09 at 17:49 +0200, Andrew Ammerlaan wrote:
(de)compressing modules changes the path of the module files so we need to
run depmod to ensure that tools such as modprobe/modinfo work.
Note that depmod is often, but *not* always, run by sys-k
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
On Fri, 2024-08-09 at 17:49 +0200, Andrew Ammerlaan wrote:
> (de)compressing modules changes the path of the module files so we need to
> run depmod to ensure that tools such as modprobe/modinfo work.
>
> Note that depmod is often, but *not* always, run by sys-kernel/installkernel.
> Systemd insta
On 8/9/24 11:59 AM, Maciej Barć wrote:
> 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 I
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
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 instal
(de)compressing modules changes the path of the module files so we need to
run depmod to ensure that tools such as modprobe/modinfo work.
Note that depmod is often, but *not* always, run by sys-kernel/installkernel.
Systemd installs a hook to do this, but there is no equivalent on openrc
systems.
El vie, 09-08-2024 a las 16:40 +0100, Sam James escribió:
> Hi!
>
> Some packages like libffi, gcc support extended, slower versions of
> their testsuites. In the past, I've seen both USE="expensive-tests"
> (I
> think) and USE="test-full" (used in a few places in-tree atm) for
> this.
>
> I sort
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?
Hi!
Some packages like libffi, gcc support extended, slower versions of
their testsuites. In the past, I've seen both USE="expensive-tests" (I
think) and USE="test-full" (used in a few places in-tree atm) for this.
I sort of hate both suggestions but I'm open to what people think is
best, with a
10 matches
Mail list logo
