On Sun, 2008-04-20 at 14:58 +0200, Martin Fuzzey wrote: > Hi mentors, > > A little question regarding automatic test suites : > > When a package provides such a suite should the normal package build process : > > 1) Always run the test suite (for example to catch bugs that may not > occur on the developper's architecture)
Yes. (That is the main point of having a test suite.)
> 2) Never run the test suite (to avoid "wasting" buildd time)
No.
> 3) Run the test suite provided its resource usage is "reasonable"
> (what is reasonable??)
A broken test suite should be fixed, not disabled.
> As a related question:
> If the test suite requires extra packages that would not otherwise be
> needed but the test suite is NOT run as part of the build process
> should they be listed in Build-Depends anyway? If not how should the
> requirements be documented? (maybe there should be a field
> "Build-Suggests"...)
The test suite should be run by the buildd so the dependencies of the
test suite are the build-dependencies of the source package.
Always run the test suite - *except* if the nocheck option is passed to
DEB_BUILD_OPTIONS so that it can be easily disabled when cross building.
ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
make check
endif
http://wiki.debian.org/EmdebianGuide
--
Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
signature.asc
Description: This is a digitally signed message part
