OoO En ce début d'après-midi nuageux du dimanche 20 avril 2008, vers 14:58, "Martin Fuzzey" <mfuzzey@gmail.com> disait: > 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) > 2) Never run the test suite (to avoid "wasting" buildd time) > 3) Run the test suite provided its resource usage is "reasonable" > (what is reasonable??) > 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"...) I don't know what reasonable means. However, if you want to run tests (which is better than not running them), check that the variable DEB_BUILD_OPTIONS do not contain "nocheck" keywork. For example, you can add this kind of snippet to your Makefile: ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS))) [...] endif You should then add any dependency needed to run tests in Build-Depends. -- I WILL NOT BRIBE PRINCIPAL SKINNER I WILL NOT BRIBE PRINCIPAL SKINNER I WILL NOT BRIBE PRINCIPAL SKINNER -+- Bart Simpson on chalkboard in episode 8F03
Attachment:
pgpbxWcJJNX9O.pgp
Description: PGP signature