[Clfs-dev] Test Suite commands

[William Harrington]

On Nov 19, 2013, at 2:04 AM, Pierre Labastie wrote:

> Le 18/11/2013 23:07, William Harrington a écrit :
>> Greetings,
>>
>> All of our test suite commands that are not required do not have a  
>> box around them because I think the developers at the time only  
>> were concerned with the required test suite commands being dumped  
>> during the "make dump-commands" with the book's XML.
>>
>> As it stands now, all non required test suite commands do not have  
>> a box around them.
>>
>> I'm going to test with jHALFS to make sure that adding <userinput>  
>> tags around the test commands don't interfere with it's build  
>> process.
>>
>> [...]
>
>> I do not think it will affect jHALFS builds, as the xsl for clfs in  
>> that system will fix that along with the build scripts for jHALFS,  
>> but users who have built their own build scripts around it will  
>> need to add commands to remove the test commands if they don't need  
>> them.
> Right now, the CLFS.xsl seeks non required test instructions in  
> <para><command> tags, while it considers that instructions  
> containing "check" or "test" in <screen><userinput> tags are  
> required tests (with a few exceptions like coreutils for example). I  
> suggest you include a remap="test" attribute in the <userinput>  
> tags, for easier parsing, if you'd make the move to those. Thanks.
>
> Regards,
> Pierre
>

That sounds like a good plan. I'll see about doing that in the future.

Sincerely,

WIlliam Harrington