Autodetecting insufficiently hardened builds (was: New hardened build support (coming) in F16)
Matthew Garrett
mjg59 at srcf.ucam.org
Tue Aug 9 14:58:13 UTC 2011
On Tue, Aug 09, 2011 at 04:53:16PM +0200, Björn Persson wrote:
> Matthew Garrett wrote:
> > Unless the checking is part of autoqa this simply isn't
> > sufficient. There's a huge benefit to implementing it in the way that's
> > easiest for maintainers.
>
> The earlier a problem is detected, the cheaper it is to fix. If I have
> understood AutoQA right, it gets involved only after I submit a package to
> updates-testing. Even better, when possible, is to detect problems during the
> build, so that I notice them when I test-build locally and can fix them before
> I even commit the changes to Git. Some checks are already done at build time,
> and Steve's points 1, 2 and 4 look like they should be possible to detect at
> build time too.
Checking at build time is a developer aid, but doesn't prevent mistakes
from slipping into the distribution. Having both would certainly be
helpful.
--
Matthew Garrett | mjg59 at srcf.ucam.org
More information about the devel
mailing list