On Sun, May 05, 2013 at 12:18:44AM +0100, Wookey wrote:
> The harder question is how/when to do that QA.
The time to do QA is now and always. Otherwise it just collects and
becomes too much.
> I resisted making the
> suggestion of doing it by default on all builds as that seemed a step
> too far, although I see someone else did :-). In fact, given the
> significant overhead of build-dep installation, build-twice would
> actually be quite a small overhead for many smaller packages (and only
> needs to be done on one fast arch, not all of them). It would clearly
> be annoying for builds that are large/slow anyway, which implies some
> kind of exception list, which was kind of the point where I decided
> this wasn't going to fly.
If one arch tests it that should be enough for 99% of cases. So
limiting it to fast archs should be fine. This could even be done
dynamically. Use --build-twice only if there are less than X source in
needs-build. In times of stress and on slower archs the option would
be droped automatically.
>From time to time archive wide rebuilds are done. Those could
certainly do --build-twice if buildds don't.
MfG
Goswin
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130508102045.GF13185@frosties
