  On 2013-02-01 at 06:53:33 [+0100], Landon J Fuller
<landonf@xxxxxxxxxxxxxx>  > Now, imagine it's a bit more complex
-- you need to be able to quickly test  > changes to ICU that
affect LocaleKit, which means you need to build both,  >
repeatedly. A build bot isn't an option there, so what you
really need is a  > way to do this automatically, and then
rebuild LocaleKit, as part of a  > standard compile+run test
cycle.  You don't do it this way. Instead, you run Haiku,
checkout both ICU and Haiku  sourcecode, and build just ICU and
libbe. You put them both in a "lib" dir  next to your test
executables. And you don't even have to reboot to test your
When this is not possible, we have tools to do it anyway. For
example, there  is the test_app_server environment which allows
to test changes to app_server  and decorators.  > Or, let's say
you're trying to test an experimental new compiler (say, a  >
beta version of clang where you've implemented support for the
legacy gcc2  > CXXABI, or in my case, a fatelf-cap