Well, putting it gently you have a good product and one of (maybe, the)
worst manual on earth describing it. You cant argue that as a volunteer
effort you depend on volunteers, because you have volunteers willing and
wanting to put their backs to the wheel to improve your manual, e.g.,
http://lis
On 1 April 2015 at 00:35, Arthur Schwarz wrote:
> Well, I've never done a patch. More appropriately, the Automake document
> needs a thorough review and rewriting. I don't have the knowledge to do
> that, I don't know automake. More appropriately, the patches would be more
> extensive then just ca
On 28 March 2015 at 23:54, Arthur Schwarz wrote:
> Win7-64 bits
> Cygwin
> Automake 1.14, Nov 2013
>
> 15.2.3 Parallel Test Harness
> Pg. 113
>
> "TEST_EXTENSIONS defaults to .test; it can be overridden by the user ..."
>
> All examples indicate that this is a developer variable, and the body of
On 2 April 2015 at 17:41, Arthur Schwarz wrote:
> Win7-64-bit
> Cygwin
> Automake 1.14.1
>
> The example given on the page has:
>
> % cat configure.ac
> o o o
> AC_REQUIRE_AUX_FILE([tap-driver.sh])
>
> o o o
>
> % cat Makefile.am
> TEST_LOG_DRIVER = env AM_TAP_AWK='$(AWK)' $(SHELL) \
> $(to
-Original Message-
From: Gavin Smith [mailto:gavinsmith0...@gmail.com]
Sent: Saturday, April 25, 2015 5:31 AM
To: Arthur Schwarz
Cc: Automake Mailing List
Subject: Re: API for Custom Drivers
On 25 April 2015 at 13:11, Arthur Schwarz wrote:
> >> In "15.3.2 Declaring Custom Test Drivers"
On 25 April 2015 at 13:11, Arthur Schwarz wrote:
>> In "15.3.2 Declaring Custom Test Drivers" we have the automake variables
>> LOG_DRIVER and ext_LOG_DRIVER. Assuming LOG_DRIVER = driver, does the
>> statement mean that to execute "driver" I type:
>>
>>make driver
>>
>> Instead of
>>make
-Original Message-
From: Gavin Smith [mailto:gavinsmith0...@gmail.com]
Sent: Saturday, April 25, 2015 1:26 AM
To: Arthur Schwarz
Cc: Automake Mailing List
Subject: Re: API for Custom Drivers
On 25 April 2015 at 00:27, Arthur Schwarz wrote:
>
> In "15.3.3.1 Command-line arguments for te
On 13 April 2015 at 20:34, Arthur Schwarz wrote:
> I am very much a novice at this so if I have made (some) mistake(s) please
> tell me how to correct them.
>
> I have a suggested change to the general introduction given in Section 15
> "support for test suites" section of the manual. Before I pro
On 25 April 2015 at 00:27, Arthur Schwarz wrote:
>
> In "15.3.3.1 Command-line arguments for test drivers" there is the
> statement:
>
> "The first non-option argument passed to the test driver is the program to
> be run, and all the following ones are command-line options and arguments
> for this
On 25 April 2015 at 00:13, Arthur Schwarz wrote:
>
> 15.3.3.1 Command-line arguments for test drivers
>
> --color-tests={yes|no}
>
> Is 'always' an option? See 15.2.1 Scripts-based Testsuites
> "AM_COLOR_TESTS=always"
>From my reading, if AM_COLOR_TESTS=always, then --color-tests=yes will
be pas
On 25 April 2015 at 00:04, Arthur Schwarz wrote:
>
> In 15.3.3.1 Command-line arguments for test drivers
>
> --log-file=PATH.log
>
> The .log file the test driver must create (see Basics of test metadata).
> If it has a directory component (as in e.g., sub/foo.log), the test harness
> will ens
11 matches
Mail list logo
