Load templates and definitions

We should load the templates and defs before trying to display them.
Remove definition option
Unignore defintions and templates.

I think it would be useful to keep the defintions and templates under source
control so I'm going to unignore them.
Add some definitions

These are some simple definitions that I think should come with prj. They are
for basic files, directories, scripts and general system commands. These are
pretty basic but work well enough for me now.
Simplify update

Update should be much cleaner. In addition, I'm going to rename template to
blueprint as templates will be file level, while blueprints will be project
level. This new update is what I want it to look like. It doesn't work yet but
this is the skeleton I will fill in.
Update to expected API

We should rename template to blueprint as needed. In addition, I added a TODO
about where I should have file templates.
Move to using blueprint

I'm changing a couple things here. First, I'm making the cosmetic change of
going from template to blueprint. Secondly, I'm changing what the blueprints
are. Before they were a file with a bunch of statements in them. Now I'm moving
them into a single macro. This lets me put many such definitions in a single
file as well as have my blueprints be scheme and not some schemish dsl.
Load the blueprint module

It was renamed and moved so we reflect those changes.
Update list to new API

List now uses the simplier API.
Remove unneeded imports
Reflect name changes.
Ignore blueprints directory

We don't need to keep those under source control so we will ignore them.
Add a simple basic test

Tests are good. This tests the very basic functions of making blueprints and
components.
Add test to check for component execution

Simple test to see that the component can be executed.
Update run.scm to run all tests

The run.scm file should run all tests in the tests directory. This assumes we
are running from the base directory and that all tests end in -test.scm
Add simple Rakefile

I want to use rake to run all tests for my subs. This rakefile runs the tests
and does nothing else.
Add a simple functional test

This test just checks that we can load blueprints and the like from files
correctly and store them. We've also moved around some of the test files.
New version of the blueprint library

This has been updated to fixes problems from the tests.
Use a Makefile for testing

Rakefiles will conflict with using rake to deploy.
Use phony to force test to run