-
Notifications
You must be signed in to change notification settings - Fork 0
If you want your own easyconfig files to be included with easybuild, you must
fork the easybuild repo and send a pull
request. Note: pull requests should be send to the develop branch instead of
the master branch.
Yes, use the PythonPackageModule to build different version without rebuilding Python.
Yes, if you create an easyconfig file with no sources and only dependencies. You could ofcourse also just create the module file yourself.
Easybuild tries to be smart about this and will look inside the $PYTHONPATH to find the required files. The a-z/ directory structure is entirely optional, but suggested as it keeps things organized.
Currently easybuild's support for OS dependencies is lacking. It will try to find it using rpm and dpgk, but this is not perfect. If you know what you are doing, you can remove the OS dependency from the easyconfig file, and then build it.
Because Easybuild follows the CapWords
convention, this is indeed impossible.
A work-around would be to create a 'R_' easyblock and specify this inside the
easyconfig file with easyblock="R_".
Yes, but better if you not, they are not really portable: A better way around is to actually create a .eb file for the dependency without a sources field.
You can add a sanitycheckcommand to check if the package is available (it would be nice if this is distribution independend)
This way
- a build will fail without the os dependency available.
- you can later override default tcsh with a custom build one when in need
- reduce dependencies on OS repositories and distro specific mechanisms
- actually report problems when there are exact version dependencies (otherwise a default yum/repo update can break a working HPC application).