Converting documentation index to simple index.html file

It is silly to use DocUtils to generate a simple index.thml file.  Also,
DocUtils does not allow you to create multiple <a href="<link1>" PDF</a>, <a
href="<link2>" PDF</a>, etc. in the document.  This is stupid.

Just get rid of the fluff and have a simple index.thml file.
Removing assumption of a 'tribits/' base dir (Trilinos #6218)

Once I allow TriBITS to be specified as a package as <projectDir>/TriBITS, you
have to make this change for the tests to pass.
Allowing for abs pakage directories under project source dir (Trilinos #6218)

These changes were done in order to support Trilinos or other projects pulling
in TriBITS as a package from the absolute variable ${PROJECT_NAME}_TRIBITS_DIR
variable.

I added a pretty good unit test and updated the documentation.
Print out <Project>_TRIBITS_DIR

This is good info to print in the basic configure output.
Adding --no-rebase --no-append-test-results
Mention where to find egdist in TriBITS source tree
Fixing a few simple typos
Fixing mispellig of PACKAGE_ABS_DIR_UNDER_PROJECT_SOURCE_DIR (Trilinos #6218)

Brent noticied this as part of a problem with automated testing but this was
not causing any problems.
Allow <Project>_TRIBITS_DIR to be provided as a relative path (Triinos #6218)

This allows a little easier setup for TriBITS/Trilinos co-development by just
having to set:

   -D<Project>_TRIBITS_DIR:STRING=TriBITS

and not the full path.  Note the warning about forgetting to use 'STRING'
above.
Adding the origin dir repo name and SHA1 to commit summary, listing tracking branch

With this commit, I added the name of the origin repo dir name and the origin
repo SHA1 to the commit message summary.  Now this looks like:

    Automatic snapshot commit from TriBITS at c8d7a01

instead of just

    Automatic snapshot commit

I also updated the script to find out the remote tracking branch and dislay
that instead of assuming origin/master.
fix relative path in project export files

The earlier commit 6d07ec56bc83c3e1e085ec33cec089bc49595f07 already fixed
relative paths in export files for package export; this commit does the same
for project export files.

See Trilinos bug #6181.
add basic travis-ci file
do out-of-source build
travis-ci: add fortran compiler
Adding some vertical whitespace to standardized formatting
Fixing nasty bug where TriBITS checkin-test.py config used instead of project's (TriBITS #5)

As explained in the TriBITS Github issue #5, The TriBITS checkin-test.py
configuration was always getting used instead of the proejct's configuration
file.  This was caused by the commit:

  5c2aa1d "Allow for usage of the checkin-test.py script for TriBITS itself."
  Author: Roscoe A. Bartlett <bartlettra@ornl.gov>
  Date:   Fri Sep 5 15:58:24 2014 -0400 (4 days ago)

  A       project-checkin-test-config.py

which exposed a latent defect added way back when TriBITS was first split off
from Trilinos. The problem was that the base directory for the found
<projectDir>/project-checkin-test-config.py was append *not* prepended to
sys.path before including the module with:

    __import__(moduleName).configuration

This was very bad becuase the TriBITS base path automatically gets *prepended*
by python into sys.path just by the checkin-test.py script running the
checkin-test.py script.  Therefore, when I added the file:

   TriBITS/project-checkin-test-config.py

which got snapshotted to:

   Trilinos/cmake/tibits/project-checkin-test-config.py

this logic resulted in this file getting selected for the project's
checkin-test.py configuration file, not the project's:

   Trilinos/project-checkin-test-config.py

file.

By picking up the TriBITSProj project's project-checkin-test-config.py file,
it got --enable-packages=TriBITS and also ignore all of the other
Trilinos-specific MPI_DEBUG and SERIAL_RELEASE options.  Very bad.

Also, as part of this commit, I figured out how to set the default for
--src-dir to the same directory where the project's
project-checkin-test-config.py is found.  That means that checkin-test.py will
automatically pick up the projects project-checkin-test-config.py file as long
as the checkin-test.py script is symlinked into the project's base directory
tree, no matter where it get TriBITS from.  This also allows the
checkin-test.py script under the TriBITSProj build to automatically find the
right project directory.

This is really a great commit if you take this all in!

For GitHub: Fixes #5
Adding all checkin-test.py defaults to config file and removing checkin-test.py (Trilinos #6218)

Now that checkin-test.py will correctly pick up --src-dir given the localtion
of the found project-checkin-test-config.py in the base directory, there is no
longer any reason to have a generic checkin-test.sh wrapper.  Therefore, I
have added the defaults --no-rebase --no-append-test-results directly to the
TriBITSProj project's configuration file.

Now you can push to TriBITS by directly calling the checkin-test.py script and
not bother with a wrapper script.  That will work fine as long as the
compilers and MPI are in your default path.
Merge remote branch 'nico-github/travis_ci'
Merge branch 'master' into export_include_dir
Merge pull request #7 from nschloe/export_include_dir

fix relative path in project export files