On Mon, Oct 21, 2013 at 10:40:12AM -0400, Joey Hess wrote: > Steve Langasek wrote: > > I'm filing a bug against debhelper asking for this behavior to be reverted. > > debhelper should *not* automatically disable the test suite when > > cross-building. There are perfectly legitimate cases where you may be > > cross-building and *do* want to run the test suite, and this behavior change > > in dh undermines this. If someone wants the test suite to be skipped > > because they're cross-building, they should use the standard interface for > > this and set DEB_BUILD_OPTIONS=nocheck. Whereas if someone does want the > > test suite to be run when cross-building, there is no corresponding > > interface that lets them override this in the other direction.
> > Joey, could you please revert this change to debhelper? (Added in response > > to bug #703262; cc:ing that bug's submitter.) > It seems to me that most test suites involve running the program from > the package, which would be difficult to do when cross building; and even > if it somehow works, would not be testing it on the destination system. That would depend entirely on what you're cross-compiling to. If you're cross-compiling from amd64 to i386, there's no reason not to run the tests. If you're cross-compiling to armhf, you may want to run the tests under qemu. This should be left up to whoever is setting up the cross-build environment, and not hard-coded in debhelper. > But, I don't have a strong opinion about this, and don't feel debhelper > has any obligation to avoid breaking cross building packages whose test > suites are like that, so I'll make a change if it's generally agreed on. Does Bastien's response suffice to establish this as "generally agreed"? Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected]
signature.asc
Description: Digital signature
