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.

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.

-- 
see shy jo

Attachment: signature.asc
Description: Digital signature

Reply via email to