On Mon, Nov 19, 2012 at 10:07:40AM -0700, Bdale Garbee wrote: > Daniel Holbach <[email protected]> writes: > > > it'd be great to enable autopkgtest tests for gzip as it's an essential > > part > > of any system. I took the liberty to write an (admittedly) very simple > > autopkgtest and add it to the package. > > Is there some reason you're ignoring the package's existing test suite? > > While I hadn't been paying attention to it, now that I've read about it > I certainly don't object to the concept behind dep8. But it makes no > sense at all to start creating separate tests when the upstream package > source already includes a credible test suite, as is the case with gzip. > The current gzip debian/rules file invokes the test suite using 'make > check' and the package build will not complete if any of the tests fail > on the as-built executable. > > So, I'm not interested in merging this patch as-is. If it can be > reworked to run the existing test suite on an autopkgtest testbed, then > I'd be willing to merge such a patch. If that's not possible, then I > suggest the design of autopkgtest be revisited so that we don't need to > replicate and/or diverge from upstream test suite creation and management.
I'm not aware which patch is under discussion, but note that autopkg tests are orthogonal to build tests. They are designed to test that after a package has been installed, it has been correctly installed, rather than/on top of being correctly built. I don't know if this applies to gzip, but there's is a definite separation between build and install tests at least for other software. regards, iustin
signature.asc
Description: Digital signature
