-
Notifications
You must be signed in to change notification settings - Fork 25
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 Externals_BLOM.cfg file for use with NorESM2.3 #471
Add Externals_BLOM.cfg file for use with NorESM2.3 #471
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for converting back (and adjust for the most recent version)!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Side question: If you had a choice, would you like to have a pure manage-externals like solution (i.e., externals file, does not use submodules to check out externals), git fleximod as it is today, or a hybrid tool that uses an externals file along with submodules?
@gold2718 thanks for asking. I might be missing the point of |
@jmaerz, You are basically correct. The original motivation was the feeling at NCAR that manage_externals was too time consuming to maintain. manage_externals was written at a time when many externals were in subversion repositories and also when git submodules were not as mature as they are now. However, the community has a strong desire to have explicit documentation and control of the tags used in each external. Note that BLOM is free to use submodules without including I have started a discussion on what features we need / want for our external checkout tool. I believe it includes the synchronization features you describe above. |
This PR re-introduces the
Externals_BLOM.cfg
file, so that we can use the currentmaster
branch (currentlyv1.7
tag and potentially the upcomingv1.8
tag) in NorESM2.3.See discussion in #470