On Sun, Sep 18, 2016 at 08:07:14PM +0300, Adrian Bunk wrote:
> The only controversial cases seem to be tests, and these can run
> optionally after the packages have been built.
> Has anyone already thought of moving such tests into a separate optional 
> step after the build is completed?
> What I have in mind is the last lines of dpkg-buildpackage output being:
>   This package contains optioal tests that might access the network.
>   You can run them separately using
>     dpkg-buildpackage --run-network-tests
> Commandline parameter, DEB_BUILD_ option or buildpackage.conf might also 
> define that they run automatically after building the packages - this is
> then your personal policy, and autobuilders are also able to run the 
> tests if they want to.

Good idea!

What about just DEB_BUILD_OPTIONS=network [1]?  That would require no
changes to any tools, and be consistent with other tags like nocheck, noopt,
nostrip or parallel.

[1]. Chosen for brevity, you may prefer something more descriptive.
Second "wet cat laying down on a powered-on box-less SoC on the desk" close
shave in a week.  Protect your ARMs, folks!

Reply via email to