On Mon, Oct 21, 2013 at 10:38:07AM +0200, Bastien ROUCARIES wrote: > On Mon, Oct 21, 2013 at 3:29 AM, Steve Langasek <[email protected]> wrote: > > Package: debhelper > > Version: 9.20130504
> > On Sun, Aug 18, 2013 at 06:20:03PM +0800, YunQiang Su wrote: > >> Hi, Steve, > >> dh_auto_check disable check when cross build by default now, when cross > >> build, I believe it's a good behavior. > >> Here we override_dh_auto_check, fellow the behavior of dh_auto_check > >> will be a good idea. > > Thanks for making me aware of this. > > 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. > Could we add nocheckcross option in this case ? Why? Either option would be something you need to set up in your cross-build environment. Why not just use the existing 'nocheck'? If you want a more nuanced option to express that we should skip only test suites that require running binaries for the target architecture, then we could add something... but such an option should be discussed on the policy list first and would take some time before it becomes well supported. -- 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
