Modular library design

Looking at the following directory trees:

master
origin/unittests
origin/devl-2_0
sanak/pgrouting4w
mbasa/pgrouting
postgis

Here is my initial take at a new directory structure:

pgrouting/
  core/           - I'm not sure this adds a lot of value but keeping
                    the root of the tree simple is probably a good idea.
    <pkg>/
      doc/        - restructured text doc files
      src/        - compiled source files
      sql/        - low level sql wrapper
      test/       - unit test files and harnesses
  cmake/
  regress/        - sql files to do in databse regression testing
  CMakeFiles/
  DIST/          - directory to hold distribution specific files
    debian/
    rpm/
    windows/

Where would be like:

apsp
astar
common             - this assumes that we share a lot
darp
dijkstra
driving_distance
graphic_analytics
shooting_star      - probably drop this
trsp
tsp                - expose just the tsp solver
wrappers           - this could be for high level sql wrappers

This will probably change some as I start working with and find that it is awkward to get it to build or get feedback from others.