On 2023-06-06 15:11, Bruno Haible wrote:
There are at least two problems here:
* A logic that distinguishes two types of environments (e.g. git checkout
vs. tarball) increases the test requirements
We need to support both environments. But the more similar they behave
Paul Eggert wrote:
> >* Compilations from a git checkout and compilations from a tarball
> > behave the same way.
>
> They can behave differently if the person checking out from git (or
> building from a tarball) has a different environment from the person who
[Original problem report in [1].]
See on the hydra build:http://hydra.nixos.org/build/256086
Hydra creates its tarballs not directly from the git checkout, but by running
in particular make dist in the git checkout.[2] This has caused problems
also in other packages.
Specifically in autoconf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Would anyone object if I created .cvsignore and .gitignore that ignore the
pattern testdir*? That way, it would be easier to do in-tree tests with
'./gnulib-tool --with-tests --test ...' without seeing spurious untracked
items when a test fails and
Eric Blake wrote:
Would anyone object if I created .cvsignore and .gitignore that ignore the
pattern testdir*? That way, it would be easier to do in-tree tests with
'./gnulib-tool --with-tests --test ...' without seeing spurious untracked
items when a test fails and leaves behind a directory.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bruno Haible on 4/12/2007 4:36 PM:
Eric Blake wrote:
Would anyone object if I created .cvsignore and .gitignore that ignore the
pattern testdir*? That way, it would be easier to do in-tree tests with
'./gnulib-tool --with-tests
