Skip to content

nightly: Support relative submodule paths #54

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

Conversation

bwbarrett
Copy link
Member

GitPython's internal submodules support is not a direct call to
the underlying git submodule interface, but does a bunch of
magic that we do not need. It also does not support relative
paths, which are now used in OMPI's submodule definition. Switch
to using the underlying git submodule calls directly to fetch
the submodules.

Using the underlying submodules command required us to have a HEAD
that is in refs/ as a local branch. Change the checkout command
so that the branch we are building is a local branch to stop
irritating git submodule commands.

Signed-off-by: Brian Barrett bbarrett@amazon.com

GitPython's internal submodules support is not a direct call to
the underlying git submodule interface, but does a bunch of
magic that we do not need.  It also does not support relative
paths, which are now used in OMPI's submodule definition.  Switch
to using the underlying git submodule calls directly to fetch
the submodules.

Using the underlying submodules command required us to have a HEAD
that is in refs/ as a local branch.  Change the checkout command
so that the branch we are building is a local branch to stop
irritating git submodule commands.

Signed-off-by: Brian Barrett <bbarrett@amazon.com>
@bwbarrett bwbarrett requested a review from jsquyres October 8, 2021 18:37
@jsquyres jsquyres merged commit cd78a5c into open-mpi:master Oct 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants