tree rearrangment proposal...

OK, so Karl is implementing Change #8, and has run into a circular
dependency problem. We have a proposed solution, but first let me
explain the problem:

   * Change #8 was jimb's suggestion that libsvn_delta create a single
     "dummy" editor full of "dummy" routines. Any other routine that
     needs to implement an editor simply summons this dummy editor and
     inserts new routines. (This make editor interface changes much
     easier in the future.)

   * tests-common/ implements a standard `test' editor used by many of
     the tests/ subdirs within libraries. This `test' editor now
     depends on summoning the libsvn_delta `dummy' editor (just as any
     editor would.)

   * When we try to build libsvn_delta, the build system tries to
     build everything in libsvn_delta/tests/, which depends on
     tests-common/ to be built, which in turn depends on libsvn_delta
     to be built. QED.

Our proposed solution is to move every `tests/' subdir OUT of each
library directory and into tests-common/. This is clean, in the sense
that tests-common will not only contain a common test-harness code,
but a subdir to test each library component of subversion. All the
tests are in one place, which is nice for `make check', as well as QA
people.

Karl has volunteered to do all the repository munging necessary (to
preserve history and tags.) In theory, once he's done, a simple `cvs
up -dP' should be all we need to do.

Thoughts?
Received on Sat Oct 21 14:36:20 2006