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

add support for 'clone_into' field in git_config source spec to specify different name for top-level directory #3949

Merged

Conversation

akesandgren
Copy link
Contributor

There is at least one software (avogadrolibs) that assumes that the directory
the repo is cloned into has a different name than the upstream repo.

There is at least one software (avogadrolibs) that assumes that the directory
the repo is cloned into has a different name than the upstream repo.
@akesandgren akesandgren added this to the 4.x milestone Jan 31, 2022
Copy link
Member

@boegel boegel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@akesandgren Looks good, but the test for get_source_tarball_from_git in test/framework/filetools.py should be enhanced to verify that using clone_into has the desired effect, and the documentation should be updated too (see https://docs.easybuild.io/en/latest/Writing_easyconfig_files.html#common-easyconfig-param-sources-git-config)

@boegel boegel changed the title Add a "clone_into" field to git_config source specification. add a "clone_into" field to git_config source specification Feb 16, 2022
@boegel boegel modified the milestones: 4.x, next release (4.5.4?) Feb 16, 2022
@boegel boegel changed the title add a "clone_into" field to git_config source specification add support for 'clone_into' field in git_config source spec to specify different name for top-level directory Mar 1, 2022
@boegel boegel merged commit 907e625 into easybuilders:develop Mar 1, 2022
@akesandgren akesandgren deleted the add_clone_into_to_git_config branch March 2, 2022 06:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for using a name different from the git repo name during clone
2 participants