Naming Scheme for Source Directories

Everything in the code is an item for the potential to have plugins. We will keep a clean naming scheme for this reason.

For the server the naming is "drizzled"

So an install will be:
/usr/local/include/drizzled/

Client library:
/usr/local/include/libdrizzle

* Why drizzled over just plain drizzle?

If we add extensions to the command line library they will go into "drizzle"

* Ramifications for includes?

Includes that will be installed need to be written like:
#include <drizzled/field/blob.h>

The use of:

#include "item.h"

Should only be used in cases where we are to never install these libraries in the filesystem.

TODO: Work out "error" condition in includes if a build of the server uses an "include" from the install path (aka we want to make sure we only use the includes in our directory).