Hi Mike,
Sorry for not responding to this earlier...
On 22/04/2020 01:13, Mike Kelsey wrote:
Howdy! I'm new to EB, but have been doing some development work and
submitting PRs in the last few weeks. My latest is a modification in
EB-framework itself (see issue #290), which I'd like to test before
submitting a PR (a radical notion, to be sure).
I already have all four repositories checked out, and I'm wondering how best
to "install" EB from those repos for me to run with my modifications. The
various options in the docs, including install-EasyBuild-develop.sh, all
seem to assume that I want to download either from PyPI or GitHub, which I
don't. Should I just modify install-EasyBuild-develop.sh to skip the
download parts, or is there an easier way?
If you're making changes to the EasyBuild framework itself, the easiest
way is to just have a checkout of the easybuild-framework repository
(where you've made your changes) listed (first) in your $PYTHONPATH.
So, if you have cloned the easybuild-framework repository into
$HOME/example/easybuild-framework, just do:
export PYTHONPATH=$HOME/example/easybuild-framework:$PYTHONPATH
There are a few caveats here in case you have another EasyBuild
installation in place, depending on how it was installed (anything
provided through a module is fine, but if it was installed system-wide
or in your home directory via "pip install --user", you may need to
convince Python to ignore those installations, for example via "python -S").
For modified/additional easyblocks, just use --include-easyblocks (see
https://easybuild.readthedocs.io/en/latest/Including_additional_Python_modules.html#including-additional-easyblocks-include-easyblocks).
For modified/new easyconfigs, just point 'eb' to their location (either
directly on the command line, or via --robot if you need them for
dependencies).
regards,
Kenneth
-- Mike Kelsey
