Hi Collin,
> $ gnulib-tool --tests-base testsuite --copy-file tests/init.sh
Ah, that's what you meant. Indeed, that should work.
> Though this would work too and is probably more clear:
>
> $ gnulib-tool --copy-file tests/init.sh testsuite/init.sh
Yes, this is clearer, because the `gnu
Bruno Haible writes:
>> So I think it is worth mentioning
>> that projects like sed will need to use the --tests-base option.
>
> No, that would add constraints between things that better stay
> independent:
> - the import of Gnulib tests into the package (if desired),
> - the use of init.sh
Collin Funk wrote:
> I don't see that option used much.
GNU poke uses it in bootstrap.conf.
> So I think it is worth mentioning
> that projects like sed will need to use the --tests-base option.
No, that would add constraints between things that better stay
independent:
- the import of Gnulib
Hi Bruno,
Bruno Haible writes:
> Rather than having to sync this file from gnulib manually, it would
> be better if the 'bootstrap.conf' file of each of the packages
> would contain an invocation of
> gnulib-tool --copy-file tests/init.sh
> This would make this sync automatic.
Agreed.
I don'
Collin Funk wrote:
> If someone wants to update these packages that would be nice. :)
>
> $ find . -name 'init.sh' | xargs grep -l 'mktemp -d -t -p'
> ./cppi/tests/init.sh
> ./diffutils/tests/init.sh
> ./grep/tests/init.sh
> ./parted/tests/init.sh
> ./sed/testsuite/init.sh
> ./vc-dwim/tests/init.s
