Stephan Bergmann <[EMAIL PROTECTED]> writes:
> It follows that, in an ideal world, every CWS should then be built
> on unxlngi6, unxsol{i|s}4 (sufficiently similar so that one of them
> ought to be enough), and wntmsci10, so that build breaks are found
> early, before integration.
>
and
> However, some people build OOo in such a way that they use
> system-supplied alternatives of those external projects, so that the
> patches will have no effect for them. That means that switching on
> "warnings are errors" can break such builds (although the "official"
> OOo builds would succeed). The relevant patch files, until now, are
> boost/boost-1.30.2.patch
> boost/spirit-1.6.1.patch
> icu/icu-2.6.patch
> neon/neon.patch
> python/Python-2.3.4.patch
> sablot/Sablot-0.52.patch
> stlport/STLport-4.0.patch
> stlport/STLport-4.5-0119.patch
>
Add agg to the list.
I guess it is largely unrealistic to have every community CWS built on
the four mentioned platforms - unless we (Sun) do it ourselves (me
thinks that especially wntmsci10 will pose problems). Thus it's maybe
a bit moot to think about requesting self-contained OOo builds on top
of that (if we do it ourselves, it's for free anyway).
But what about providing tinderbox slaves, dedicated to community CWS?
Cheers,
--
Thorsten
If you're not failing some of the time, you're not trying hard enough.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
