-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add support for specifying alternative download methods #112
Comments
This was requested by a number of people during SC'12, so let's bump the priority a bit (low --> medium). |
Please don't forget about hg repositories. |
My usecase for this feature is Clang. There are revisions in the repository that received more testing, but are not released (and will never be packaged as tarballs). Clang development moves quite fast, and the latest release -- 3.2 can be considered somewhat dated now. So it would make sense to build from these revisions while fetching the source directly from VCS. |
For SVN, we should make sure support for downloading specific svn revisions is added, e.g. to download the source code for OpenSees v2.4.3:
see http://opensees.berkeley.edu/OpenSees/developer/svn.php (http://opensees.berkeley.edu/OpenSees/changeLog.php for the SVN revision that corresponds to a particular version) |
I've started on adding support for downloading over svn, see The path chosen here is: export a revision of the svn repo (like checkout but without revision information), create a tarball, put this tarball in the sources folder, just like a normal http download would do. This is already working for me, just cleaning up the code a bit now. |
Cf, #2555 |
I'll go ahead and close this, since we have support for cloning a Also supporting other methods like SVN can be done equivalently. |
(old internal ticket 317)
We need to be able to also specify alternative ways of downloading sources, e.g. checking out from a CVS/SVN/git/hg repository.
This is required for e.g. MTL4 (see issue #111), CP2K, ...
The text was updated successfully, but these errors were encountered: