On Wed, Nov 28, 2012 at 07:55:12AM +0900, Norbert Preining wrote: > On Di, 27 Nov 2012, Patrice Dumas wrote: > > Did you run the tests as part of the build? > > No. Here on my computer I run it maually, though, and get all PASS > or SKIP (a few tests are skipped). > > My feeling (but not tried) is that in the minimal environment of > Debian build-daemons there will be quite some failures due to > something missing.
But you can still add these as build requires. I guess that you have all the dependencies. Actually it looks like Unicode::EastAsianWidth is not packaged in debian, I guess the internal copy is used. The other libtext-unidecode-perl libintl-perl are available. All the additional modules needed for tests are in debian, libdata-compare-perl libtest-deep-perl, and Test::More which is in perl-modules. For the Pod-Simple-Texinfo module you need Pod::Simple::PullParser which is also in perl-modules. You also need sed, awk, diff (with -u), mktemp, and prove but I guess they are all there in your minimal build root. (As a side note, in case it still was not obvious, I use a Debian testing...) > Do you have a recommendation? Should I run the tests on all archs > during build time? No problem - if you let me know, then I can send > you the build logs and errors if necessary. It really depends on what you do usually. If you usually run tests as part of your packaging build, then you should do it, and it would even be better to check with make check ALL_TESTS=yes But if it is not customary to run tests as part of the debian build process then you don't need to. I don't know if it helps answering your question, but if I was still involved in the texinfo packaging in Fedora I would propose to run the tests as part of the build. As a side note, I would also suggest installing util/txixml2texi, which depends on XML::LibXML::Reader in libxml-libxml-perl. -- Pat
