[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Managing changes to configure.in as patches

Matt Zimmerman wrote:
> But it doesn't tell you that it's broken now; it only catches a particular
> case.  It's still quite possible for your package to silently break,
> especially if it isn't built for a while.  Even if it frequently has new
> revisions, it's also quite possible for it to end up in stable, on CDs, etc.
> where there is a different version of autotools which will break it
> (different from the one used to build it).  That breakage hides until, for
> example, someone tries to autobuild a security update for the package, and
> then has to clean up the mess.
> I think that the "lurking breakage" factor is much worse for packages which
> run autoconf during the build than those which run it ahead of time.

Not only do I test-build all my packages monthly (a simple cron job),
but there are periodic efforts to test build the whole archive for
various reasons.

see shy jo

Attachment: signature.asc
Description: Digital signature

Reply to: