[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: testdir without unportable tests?
From: |
Simon Josefsson |
Subject: |
Re: testdir without unportable tests? |
Date: |
Tue, 20 Apr 2010 10:04:40 +0200 |
User-agent: |
Gnus/5.110011 (No Gnus v0.11) Emacs/23.1 (gnu/linux) |
Bruno Haible <address@hidden> writes:
> Simon Josefsson wrote:
>> Right now I create the directory like this:
>>
>> gnulib-tool --create-testdir --with-tests --dir build
>>
>> Is there a way to avoid all the unportable tests? For example, a
>> --without-unportable-tests?
>
> I'm currently using --avoid=havelib-tests when I want to test anything that
> relies on xalloc but is otherwise unrelated to havelib.
>
> How about
> 1) change the default for --create-testdir so that it includes unportable or
> longrunning tests only for the modules explicitly listed on the command
> line, not for the dependencies?
> 2) adding options --without-unportable-tests etc.?
>
> Is this a good idea?
I prefer only 1 because it appears to be sufficient here and results in
less complexity. We could adopt the philosophy that whatever
gnulib-tool ever generates should be portable unless the user supplied
any of the --with-*-tests flags. This results in this approach:
* Change the default for --create-testdir so that it includes unportable or
longrunning tests only for the test modules explicitly listed on the command
line, not for any dependencies -- unless the corresponding
--with-*-tests parameter is given.
How about that?
/Simon