Re: using color-tests backwards-portably

2009-08-14 Thread Ben Pfaff
Ralf Wildenhues writes: > * Ben Pfaff wrote on Fri, Aug 14, 2009 at 06:33:14PM CEST: >> As an alternative, could Automake provide an API that allows >> users to say "if feature X is supported, then expand this >> configure.ac code"? For example: >> >> AM_FEATURE_PREREQ([color-tests], >>

Re: using color-tests backwards-portably

2009-08-14 Thread Ralf Wildenhues
Hello Ben, * Ben Pfaff wrote on Fri, Aug 14, 2009 at 06:33:14PM CEST: > As an alternative, could Automake provide an API that allows > users to say "if feature X is supported, then expand this > configure.ac code"? For example: > > AM_FEATURE_PREREQ([color-tests], > [AM_INI

Re: using color-tests backwards-portably

2009-08-14 Thread Ben Pfaff
Ralf Wildenhues writes: > I think Automake should provide an API to allow users to say "if the > Automake version is >= X, then expand this configure.ac code". I think > that would be general enough (it could use Automake conditionals to > adjust Makefile.am files, it could check for >= X and no

Re: using color-tests backwards-portably

2009-08-13 Thread Ralf Wildenhues
Hi Jim, * Jim Meyering wrote on Thu, Aug 13, 2009 at 08:29:21AM CEST: [...] > systems with automake older than 1.11. > On those systems, it's fine to ignore or disable these > two unsupported options. Yes. Often, automake's rejection of unsupported options is stricter than it would need to be.

using color-tests backwards-portably

2009-08-12 Thread Jim Meyering
Hi Ralf, I'd like to use automake-1.11's color-tests option in libguestfs -- and more importantly, parallel-tests, but we may have a build-from-clone requirement on systems with automake older than 1.11. On those systems, it's fine to ignore or disable these two unsupported options. I proposed a