trailing whitespace
install target export files on a per-package basis
don't reference ${PROJECT_NAME}Targets in config file
move installation of export files to add_library()

This accommodates packages with subpackages (e.g, Trilinos::Teuchos).
include subpackage exports in superpackage export files
whitespace changes (avoid superfluous newline in export)
include configuration of dependent packages in export files
Merge branch 'master' into untangle_export_files

Conflicts:
	package_arch/TribitsWriteClientExportFiles.cmake
don't explicitly include subpackage configs in export files

This reverts commit 4f36e2c793d9afd342d876600c665540c5d28ee9.

Explicitly including the subpackages' configurations isn't necessary anymore
since commit 56a93b120a65771b03b08f702f0fe6331db7aec2 which added inclusion of
*dependent* packages. Since a package always depends on its subpackages, the
functionality remains the same.
export targets only once per package, not per library
Installing CMake 2.8.11 and using github repo
Adding a standard SERIAL_DEBUG build config.
This info was copied to TribitsDevelopersGuide a long time ago

Having this document sit in the repo not being updated someone might find it
by accident and get wrong/bad info.
Implementing new Primary Meta-Project Packages (PMPP) selection (TriBITS #9)

This defines new variables:

  ${REPOSITORY_NAME}_REPOSITORY_CONTAINS_NO_PRIMARY_META_PROJECT_PACKAGES
  ${REPOSITORY_NAME}_REPOSITORY_CONTAINS_NO_PRIMARY_META_PROJECT_PACKAGES_EXCEPT

and removes the variables:

  ${REPOSITORY_NAME}_NO_IMPLICIT_PACKAGE_ENABLE
  ${REPOSITORY_NAME}_NO_IMPLICIT_PACKAGE_ENABLE_ENABLE

(which were a hack).

Also removed were the functions:

   TRIBITS_REPOSITORY_IMPLICIT_PACKAGE_ENABLE_IS_ALLOWED()
   TRIBITS_APPLY_REPOSITORY_NO_IMPLICIT_PACKAGE_ENABLE_DISABLE()

The updated behavior is deined in TriBITS Github issue #9.

This will also be fully documented in the TribitsDevelopersGuide.* document in
the next commit.

I added the macro SELECT_FINAL_SET_OF_PACKAGES_TO_PROCESS() that modifies the
set of packages that are exlicitly processed in the loop.  This makes for
nicer output and easier debugging becuase you can see exactly the packages
that will be directly processed before the loop starts and every iteration of
the loop with process a pacakge and not just skip it.

Some of the existing tests had to be modified because some strings are no
longer printed.  However, the tests should be just a strong because the look
at the final list of packages that CTest/CDash will process.

Build/Test Cases Summary
Enabled Packages: TriBITS
Enabled all Packages
0) MPI_DEBUG => passed: passed=641,notpassed=0 (36.70 min)
1) SERIAL_RELEASE => passed: passed=548,notpassed=0 (15.36 min)
Other local commits for this build/test group: 5ac058d, cb72771
Shortening of the primary meta-project packages variables (TriBITS #9x)

The variables:

    ${PARENT_REPO_NAME}_REPOSITORY_CONTAINS_NO_PRIMARY_META_PROJECT_PACKAGES
    ${PARENT_REPO_NAME}_REPOSITORY_CONTAINS_NO_PRIMARY_META_PROJECT_PACKAGES_EXCEPT

was too long to show in documentation. These were shorten to:

    ${PARENT_REPO_NAME}_NO_PRIMARY_META_PROJECT_PACKAGES
    ${PARENT_REPO_NAME}_NO_PRIMARY_META_PROJECT_PACKAGES_EXCEPT

I think they are still descriptive enough given TriBITS documentation (which
will be committed next).
Adding documentation for primary meta-project packages variables (TriBITS #9)

This completes all of the work to define the new primary meta-project packages
feature for TriBITS (Fixes #9).

Build/Test Cases Summary
Enabled Packages: TriBITS
Enabled all Packages
0) MPI_DEBUG => passed: passed=641,notpassed=0 (55.87 min)
1) SERIAL_RELEASE => passed: passed=548,notpassed=0 (8.22 min)
Other local commits for this build/test group: 23a3243
Merge remote branch 'casl-dev/master'

Conflicts:
	doc/build_quick_ref/TribitsBuildQuickRef.pdf
	doc/developers_guide/TribitsDevelopersGuide.pdf
Updated generated files.
Merge branch 'master' into untangle_export_files
Removing print of packages enables in summary email header

This commit removes the printing of the packages in the summary email
header. That list was not even correct because you can run differnet build
cases like the PT --default-builds and other ST --st-extra-builds and even EX
--extra-builds and all of these build could have different sets of enabled
packages.  You can also run the individual builds separate using different
values for --enable-all-packaes and --enable-packages.

The added benefit of removing this is that we don't have to call
getEnablesLists() a second time which is super expensive if there are a lot of
changed files and you have a lot of packages.