Skip to content
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

get cmor via git repo #1492

Merged
merged 1 commit into from Aug 23, 2015
Merged

get cmor via git repo #1492

merged 1 commit into from Aug 23, 2015

Conversation

@doutriaux1
Copy link
Contributor

@doutriaux1 doutriaux1 commented Aug 13, 2015

@dnadeau4 @aashish24 @sankhesh fetching cmor from github rather than tarball

set(CMOR_URL ${LLNL_URL})
set(CMOR_GZ CMOR-${CMOR_VERSION}.tar.gz)
set(CMOR_MD5 f7e78104878d93ffbd3cae2ccd95db2c)
set(CMOR_BRANCH master)
Copy link
Contributor

@sankhesh sankhesh Aug 14, 2015

Instead of using the master branch, it would be better to set a specific commit as the SHA-1 sum. That way, changes in the upstream repository will not break UV-CDAT

Copy link
Contributor Author

@doutriaux1 doutriaux1 Aug 17, 2015

Doing the same as for vtk/vistrails/etc... Between releases we use master, then at release time we tag a specific sha1

@aashish24
Copy link
Contributor

@aashish24 aashish24 commented Aug 17, 2015

@doutriaux1 @sankhesh sounds good to me. Having master for now is consistent.

@aashish24
Copy link
Contributor

@aashish24 aashish24 commented Aug 17, 2015

👍

aashish24 added a commit that referenced this issue Aug 23, 2015
@aashish24 aashish24 merged commit f86b869 into master Aug 23, 2015
3 of 7 checks passed
@aashish24 aashish24 deleted the cmor_via_git branch Aug 23, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants