[PATCH 1/2] prefer AM_TESTS_ENVIRONMENT to TESTS_ENVIRONMENT

, modules/update-copyright-tests: * modules/vasnprintf-posix-tests, modules/vc-list-files-tests: * modules/verify-tests, modules/wcrtomb-tests * modules/wcsnrtombs-tests, modules/wcsrtombs-tests: * tests/havelib/Makefile.am, tests/init.sh: Prefer AM_TESTS_ENVIRONMENT to TESTS_ENVIRONMENT since the

Re: [PATCH] localcharset: Use an absolute path in TESTS_ENVIRONMENT

Hi Paul, > Somehow there was a mixup in the ChangeLog entry that got > committed: the è (e-with-grave-accent) got committed as a single > byte "\350" rather than the proper UTF-8 "\303\250". I just > now fixed that. Thanks! I had applied the patch using $ git am -3 < 0001-localcharset-Use-an-a

Re: [PATCH] localcharset: Use an absolute path in TESTS_ENVIRONMENT

On 12/15/11 02:50, Bruno Haible wrote: > Hello Ludo, > >> This patch allows running unit tests that are in a subdirectory from >> another directory. > > Thanks, makes sense. Applied (with a corrected ChangeLog entry). Somehow there was a mixup in the ChangeLog entry that got committed: the è (e-

Re: [PATCH] localcharset: Use an absolute path in TESTS_ENVIRONMENT

Hi Bruno, Bruno Haible skribis: > Hello Ludo, > >> This patch allows running unit tests that are in a subdirectory from >> another directory. > > Thanks, makes sense. Applied (with a corrected ChangeLog entry). Thank you! Ludo’.

Re: [PATCH] localcharset: Use an absolute path in TESTS_ENVIRONMENT

Hello Ludo, > This patch allows running unit tests that are in a subdirectory from > another directory. Thanks, makes sense. Applied (with a corrected ChangeLog entry). Bruno

[PATCH] localcharset: Use an absolute path in TESTS_ENVIRONMENT

TCH] localcharset: Use an absolute path in TESTS_ENVIRONMENT. --- ChangeLog|5 + modules/localcharset |2 +- 2 files changed, 6 insertions(+), 1 deletions(-) diff --git a/ChangeLog b/ChangeLog index 262eeaf..abd13b8 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2011

Re: [PATCH] init.sh docs: prefer AM_TESTS_SETUP to TESTS_ENVIRONMENT

> variables for the testsuite (when the "parallel-tests" option is > used) without invading the user's namespace. > > I'd thus like to update the documentation in gnulib's `tests/init.sh' > consequently, suggesting to use `AM_TESTS_SETUP' instead of

[PATCH] init.sh docs: prefer AM_TESTS_SETUP to TESTS_ENVIRONMENT

s used) without invading the user's namespace. I'd thus like to update the documentation in gnulib's `tests/init.sh' consequently, suggesting to use `AM_TESTS_SETUP' instead of the older and not namespace-safe `TESTS_ENVIRONMENT' (which can now truly be reserved for

Re: don't augment PATH in TESTS_ENVIRONMENT

Bruno Haible wrote: >> Good catch. Thanks for doing that. >> Your patch looks right > > OK, applied. I've just pushed this correction. Sorry I didn't catch it in review. >From 3389c116ca7f63bcad9f987cdae5774b1ec2 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Sat, 4 Sep 2010 17:43:39 +02

Re: don't augment PATH in TESTS_ENVIRONMENT

Hi Jim, > Good catch. Thanks for doing that. > Your patch looks right OK, applied. > The regexp isn't as tight as it could be, but it's > adequate for now Yes, I agree. Bruno

Re: don't augment PATH in TESTS_ENVIRONMENT

Bruno Haible wrote: > It is not possible to portably augment the same environment variable twice > in TESTS_ENVIRONMENT. > > Witness: The shell command >foo=a:$foo foo=b:$foo sh -c 'echo $foo' > prints > b:a: in ksh, OpenBSD /bin/sh > a:b: in Sol

don't augment PATH in TESTS_ENVIRONMENT

Hi Jim, It is not possible to portably augment the same environment variable twice in TESTS_ENVIRONMENT. Witness: The shell command foo=a:$foo foo=b:$foo sh -c 'echo $foo' prints b:a: in ksh, OpenBSD /bin/sh a:b: in Solaris 8 /bin/sh b:in NetBSD /bin/sh and dash a

Re: TESTS_ENVIRONMENT

ppropriate for > gnulib-tool to provide these automatically. srcdir is already provided by Automake as environment variable, see (automake.info)Simple Tests: The variable `TESTS_ENVIRONMENT' can be used to set environment variables for the test run; the environment variable `srcdir

Re: TESTS_ENVIRONMENT

Hi, Jim Meyering wrote: > Currently, every test that uses init.sh must include > tests/init.sh in the "Files:" section and must append EXEEXT and srcdir > definitions to the TESTS_ENVIRONMENT in the "Makefile.am:" section: > > Files: > tests/

Re: CHARSETALIASDIR in TESTS_ENVIRONMENT?

check" before "make install" fail, unless > CHARSETALIASDIR is explicitly set in the environment. Yes. The same problem also hit the libiconv test suite. > This makes me wonder whether localcharset should recommend that a > TESTS_ENVIRONMENT something like this should be used: >

CHARSETALIASDIR in TESTS_ENVIRONMENT?

less CHARSETALIASDIR is explicitly set in the environment. This makes me wonder whether localcharset should recommend that a TESTS_ENVIRONMENT something like this should be used: TESTS_ENVIRONMENT = CHARSETALIASDIR='$(abs_top_builddir)/gl' This fixes the problem for PSPP