Christian Perrier <[EMAIL PROTECTED]> writes: [...]
> Well, what I wonder is the point of running the testsuite when > building the package. I understand that, as upstream author, you > introduce a testsuite....this is even a very good practice. > > However, I don't really see any point in running that testsuite during > builds. Moreover, from my tests, this is a very time-consuming (and > verbose) process. It's a procedure advised in the Aegis doc. I also assume that the package maintainer want to be sure that locally applied patch (not debian specific) did not change the aegis behavior and/or that aegis works correctly on the various platform debian supports. As an example of a problem catched by running the testsuite on hppa: http://permalink.gmane.org/gmane.linux.debian.ports.hppa/3767 [...] > I think it would be better to not run the testsuite. I'm not sure it will be the right choice. > The maintainer scripts seem to build with "make sure", which I guess > is responsible for the testsuite being used. > > Can you confirm this? Yes. -- Walter Franzini http://aegis.stepbuild.org/ PGP Public key ID: 1024D/CB3FEB43 Key fingerprint : FA26 C33B CAFF 7848 EFEB 7327 96AA 2D57 CB3F EB43 Key server : http://www.keyserver.net
pgprs99EvExPu.pgp
Description: PGP signature
