On Tue, Feb 14, 2017 at 04:31:22PM +0100, Jean-Pierre Chrétien wrote:
> Hello,
> 
> I discovered that quite a number of examples and templates files depend on
> resources  which do not come with TeXLive 2016. This is normal with external
> applications (R, lilypond, etc.) but there are a number of LaTeX packages
> from editors which are not in the appropriate collection of TeXLIve 2016.
> 
> I made an addition to Development.lyx to record what is needed to avoid
> ctest failures on files which are labeled as standard exports, see
> attachment.

Thanks for taking a look at the tests! And I agree, it's good to specify
all the dependencies. I have some comments below.

I think there are tests that should be labeled "nonstandard" but
currently are not. Once these are corrected, we would then change the
following sentence you added:

  With TeXLive 2016, here are the resources which should be installed to
  avoid standard tests failure:

to something like:

  Here are the resources which should be installed to
  avoid failure of tests with the "unreliable:nonstandard" label:

Do you agree?

For Development.lyx, the section
now reads:

To run all tests, in the build directory simply run the command ctest. A
full, up-to-date TeXLive installation is recommended to run the tests.
Otherwise, some tests will fail. Tests with additional requirements are
labeled "unreliable:nonstandard" [footnote: With an up-to-date Texlive 2016
installation, there are standard tests which will fail because of
missing packages or external applications, see below for a list of those
which should be installed to avoid these failures.]

I think this could be made more concise. Also, we need to be sure not to
confuse two things: (1) a *full* (I think we should mention this,
right?) up-to-date TeXLive installation is assumed for tests without the
"unreliable:nonstandard" label; and (2) for tests with the
"unreliable:nonstandard" label, there are requirements in addition to a
full TeXLive installation.

Instead of "see below", I would prefer a reference to a label.

Currently the list of dependencies you added is under the section
"4.3.1.7 What action should you take if a test fails?".
I think it would make more sense to add a section before e.g.
"Configuring the tests" that is dedicated to "Test dependencies".
What do you think?

Scott

Attachment: signature.asc
Description: PGP signature

Reply via email to