lacks, --with-tests would not uncover
> > the bug.
>
> I don't buy that either. The macro directory is shared
You're right. What I said, was bullshit.
> For reproducing the issue, it is sufficient to run
> $ gnulib-tool --with-tests --test getloadavg
> [...]
> | che
ocation that the
> library module would also need but lacks, --with-tests would not uncover
> the bug.
I don't buy that either. The macro directory is shared, there is
nothing to win here. Note this is the func_create_tests I'm changing,
not the megatest part.
I still maintain that
Ralf Wildenhues wrote:
> The patch below should some of the reported issues. OK to apply?
Thanks for this patch. Everything except the first hunk (gl_source_base)
is fine. Please apply.
About the gl_source_base of the tests directory: The idea is that
the tests directory has its sources separate
* Ralf Wildenhues wrote on Thu, Nov 09, 2006 at 12:12:27AM CET:
> It would be nice if
> gnulib-tool --with-tests --test
>
> succeeded out of the box, including actually running the tests.
The patch below should some of the reported issues. OK to apply?
FWIW, I still don'
It would be nice if
gnulib-tool --with-tests --test
succeeded out of the box, including actually running the tests. IMHO
it would make a (one) good candidate for automatic testing. Currently
it has (at least) the following issues:
- automake throws a warning about `po' not being mention
