Stephen J. Turnbull wrote:
Rather I
think we should focus on common configurations that exercise large
blocks of code that differ and aren't really optional.
That sounds like a good top priority.
Breadth in build environments also seems useful. For example, I just
set up a virtual machine with Solaris 11 (x64) on it. I can install
both gcc3 and gcc4 from Oracle's package repo. If none of the other
buildbots use gcc3, then I'd lean towards gcc3.
If we get "other" bots, maybe we should have a two-tier
system. There
would be a set of core bots (as in the previous paragraph) where we
run both a build and the tests (but only report regressions by
default), and the "other" class of bots would be configured to just
report build breakage.
Once I've got my Solaris 11 system to the point where it builds 21.5,
I'll ping Mats about getting it plugged into the buildbot system. I'm
happy to run the tests as well as simply do builds. I expect the VM to
be turned off most of the time, but I can run it when I see updates.
Anyone want to tell me which version of gcc to use? (Or suggest other
configuration options?)
mike
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta