CMake already has decent support for dependency building through External Projects:<p><a href="http://www.kitware.com/media/html/BuildingExternalProjectsWithCMake2.8.html" rel="nofollow">http://www.kitware.com/media/html/BuildingExternalProjectsWi...</a><p>There are a number of issues/annoyances with the mechanism, especially when working with local modifications, but nothing to make me eager to add the anguish of bash+CMake onto the existing toil of CMake.<p>(Arguably this also bootstraps a build environment, whereas CMake requires itself and an SDK in order to bootstrap, but at the point where a build environment needs to be scripted/reproducible containerization seems preferable)
I ask from the ignorance, no pun intended.<p>Is there a good reason to insert 30 lines of license repetition, in each script of between 4 and 10 lines of total code?<p>I see it as a maintenance/developer-usability burden (specially if the license is at the _beginning_ of each file).<p>It is not under the license of the project, if the license is not in each file?
This feels like its solving the wrong problem, package-management is effectively a version-control problem.<p>We already have our source in version-control.... we just need a way of updating and maintaining a repository with external dependencies.<p>Do any such tools exist?