See if we can use git for the dependencies

[barche]

Investigate the possibility of storing / referring to external dependencies using git. We might also be able to integrate the dependency configuration in CMake, though that would probably require rewriting the perl script in CMake.

[tlmquintino]

what would we store / do within git?
writing of the installation procedure in cmake is possible, but a bit of work.
what is the your idea / objective?

[barche]

I'd say we should store as little as possible in git, and maximally try to refer to the original software links in the dependency build script. Where and if needed, we could apply patches that are stored in our git repository (or preferably a separate git repository for the dependencies).

The objective would be to have a uniform configuration process through cmake and elimenate the dependency on the VKI serving the files for the dependencies.

[tlmquintino]

I think the packages can be kept in a central place - not store the links to original places - because it keeps the script working even if links move (can be used for longer and in retrospective for testing bygone versions).

Moreover, some links cannot be made directly (Trilinos, Mumps).

Essentially, I think we should keep away from maintaining our own "package manager" and just provide a tool (maybe within cmake) to install dependencies for users that have trouble installing them.

[tlmquintino]

If we move it towards cmake, then we can some variables:

-DCF_INSTALL_MINIMAL_DEPS=ON (for boost, openmpi)
-DCF_INSTALL_RECOMMENDED_DEPS=ON
-DCF_INSTALL_ALL_DEPS=ON

-DCF_INSTALL_DEPS_DIR=$HOME/local/arch

[tlmquintino]

We might use this: http://www.kitware.com/products/html/BuildingExternalProjectsWithCMake2.8.html