You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually, it is possible to install from a git repository directly, and without looking at the mechanisms in too much detail, I believe that this works by providing git_config at
However, I was not able to figure out how to do the same for an extension (defined within the exts_list easyconfig parameter), and I suspect that might be due to the fact that no git_config from an extension's options is passed at
Why not? Wouldn't that be useful, i.e. for installing a custom python repository via git together with its dependencies (say, standard pipy packages) in a PythonBundle?
The text was updated successfully, but these errors were encountered:
The easiest way to ensure you can use git_config for extensions is probably to make sure that sources is picked up for extensions (and then probably deprecate the custom source_tmpl which only works for extensions)...
Usually, it is possible to install from a git repository directly, and without looking at the mechanisms in too much detail, I believe that this works by providing
git_config
ateasybuild-framework/easybuild/framework/easyblock.py
Line 379 in 210743d
However, I was not able to figure out how to do the same for an extension (defined within the
exts_list
easyconfig parameter), and I suspect that might be due to the fact that nogit_config
from an extension's options is passed ateasybuild-framework/easybuild/framework/easyblock.py
Line 520 in 0b7a627
Why not? Wouldn't that be useful, i.e. for installing a custom python repository via git together with its dependencies (say, standard pipy packages) in a
PythonBundle
?The text was updated successfully, but these errors were encountered: