C4C Package Structure

Before the C4C Dev Team can start adding packages to the repository,
we need to agree on a standard folder structure.

The standard or default build method employed by Launchpad uses the GNU Makefile
method through the use of Debian build tools.

The goal of this Blueprint is to explore which method of build is most
suitable for the C4C project, and layout a standard folder / file structure that
will accommodate both the primary build method, as well as alternative
systems equally.

Three "Popular" or "Common" build systems are generally employed in Debian based
distributions:

* GNU Autotools
* Cmake
* Scons

The most popular, by far is Autotools. Cmake is seeing a higher presents in packages
that are cross-platform, while Scons is claimed to be an improved version of
Autotools, allowing for easier cross-platform work.

The following is loosely based on the traditional Autotools Model:

To get things started, the following proposal could serve as a base. This model
is normally seen in standard or more traditional ./configue, make, make install
packages. It could easily be expanded to accommodate multiple systems.

c4c-<package-name>
├── build-aux
├── data
│   ├── c4c-<package-name>.desktop.desktop
│   ├── c4c-<package-name>.png
│   └── c4c-<package-name>.xpm
├── docs
│   ├── manpages
│   ├── src
│   └── Makefile.in
├── doxygen
├── m4
├── scripts
├── src
├── AUTHORS
├── ChangeLog
├── configure.ac
├── COPYING
├── INSTALL
├── Makefile.in
└── README