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
A contributor should preferably clone the main EasyBuild GitHub repository, implement easyblocks in there and then contribute them back (see also [[Contributing back]]).
If for some reason easyblocks can not be contributed back, they can also be kept in a private easyblocks repository.
Basically, you just need to make sure these private repositories are in the PYTHONPATH, and everything should work out fine.
The text was updated successfully, but these errors were encountered:
I also removed the entry in the FAQ, since it was not entirely correct: you can't use subdirectories in your own easyblocks repo, because there's no way to flatten the namespace twice (as mentioned on the wiki page).
Well, it might be possible with some dirty hack. I haven't gotten to the bottom of it yet, and our current flattening is already kind of a dirty hack, I don't want to make it any more dirty...
(old internal ticket 215)
A contributor should preferably clone the main EasyBuild GitHub repository, implement easyblocks in there and then contribute them back (see also [[Contributing back]]).
If for some reason easyblocks can not be contributed back, they can also be kept in a private easyblocks repository.
Basically, you just need to make sure these private repositories are in the
PYTHONPATH
, and everything should work out fine.The text was updated successfully, but these errors were encountered: