move third party packages

[tlmquintino]

I think the current /include parallel to cf3/ is not convenient.
Third party packages should be in cf3/third_party or cf3/other.
When deploying then we just have to deploy the entire cf3 directory.

I vote for cf3/other

[tlmquintino]

I can do the move together with the src/ in issue #62

[wdeconinck]

Your argument is to deploy coolfluid inside a "cf3" include dir
How about our kernel plugins then? Should those now not also go in cf3/plugins/ ?
And external plugins, should then also install there?

[wdeconinck]

by the way, I vote for "cf3/external" or "cf3/deps" (in which we could also install then other third party deps) :p

[tlmquintino]

Yes, IMO, we should deploy everything inside a cf3/ directory.
Internal and external plugins should go into cf3/plugins.
Third-party packages that we are hard bound to - Eigen, fparser, etc - should go into cf3/external.
We should never install anything out of cf3/.

[tlmquintino]

cf3/external is a good place.

[tlmquintino]

My argument is also that the developer tree should be as similar to the deployment tree as possible.
The only exception will be the external plugins, but that really makes sense to exist in a a separate developer tree, since they may be hosted in a totally different source control system.