Revert container recipes to pull master #2357
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per comment in #2356.
The theory here is that:
If someone checks out the code in
3.0.3, and then builds a container using one of the recipe files, during the building of that container it should download and compile the MRtrix3 code specifically at tag3.0.3, regardless of howmastermay have changed after that point;If someone checks out the code in
master, and then builds a container using one of the recipe files, during the building of that container it should download and compile whatever the MRtrix3masterbranch is pointing to at that point in time, regardless of what tags may or may not have been added.(Better would be if, during container build, it would check out the MRtrix3 code at the commit hash corresponding to the code version of the recipe that is dictating the build process; but I have not yet thought about how such could be achieved).