Dear Jakob,
On 21/11/2018 11:12, Jakob Schiøtz wrote:
On 21 Nov 2018, at 11:09, Kenneth Hoste <[email protected]> wrote:
The problem with this approach is that some setuptools magic kicks in, causing
the easyblocks installed in your EasyBuild 3.7.1 installation to have
preference.
This doesn't happen for PythonBundle, because that's not included with
EasyBuild 3.8.0 yet...
Try configuring EasyBuild to pick up the easyblocks in the develop checkout
instead, as follows:
export
EASYBUILD_INCLUDE_EASYBLOCKS='/home/niflheim/schiotz/development/easybuild-easyblocks/easybuild/easyblocks/*/*.py'
(the single quotes are important, you should pass those literally to EasyBuild,
not let bash expand them)
See also
https://easybuild.readthedocs.io/en/latest/Including_additional_Python_modules.html#including-additional-easyblocks-include-easyblocks
for more information.
Let me know if that does the trick...
Yes, that worked! I guess I will just add that line to my .bashrc.
Thank you very much!
I should also mention "do this at your own risk".
Although we are quite careful with what is merged in develop, breakage
happens there once in a while.
Extensive regression testing on what's in the 'develop' branch is only
done shortly before a new release.
In addition, sooner or later you will run into a situation where an
easyblock that was updated requires a change in framework, which is
going to fail in your setup...
I know that several people (incl. myself) use EasyBuild straight from
the 'develop' branches, but that also includes the EasyBuild framework
itself...
regards,
Kenneth
Jakob
--
Jakob Schiøtz, professor, Ph.D.
Department of Physics
Technical University of Denmark
DK-2800 Kongens Lyngby, Denmark
http://www.fysik.dtu.dk/~schiotz/
