some time ago I did some testing to see how easybuild could be bootstrapped
using conda. This should work in any machine even if you don't have a
supported python version or a modules tool available

$> curl -o /tmp/Miniconda2-latest-Linux-x86_64.sh
https://repo.continuum.io/miniconda/Miniconda2-latest-Linux-x86_64.sh
$> bash /tmp/Miniconda2-latest-Linux-x86_64.sh -b -f
$> export PATH=~/miniconda2/bin:$PATH
$> conda install -c pescobar lmod=6.5.12 -y
$> pip install easybuild
$> source ~/miniconda2/lmod/lmod/init/bash
$> eb --modules-tool=Lmod foss-2016a.eb -r --dry-run

Pablo.


2017-04-05 19:20 GMT+02:00 Alvarez, Damian <[email protected]>:

> Alternatively, for people that regularly contribute back, you could clone
> the repo[s] somewhere in your home, write a module for it, and use it to
> install your system wide EB. We use that every time we deploy a new stack.
> It is close to trivial. This is the TCL module we have for it (and yes, it
> has tabs, I think it is the only module we wrote that has them):
>
> #%Module
> proc ModulesHelp { } {
>     puts stderr { EasyBuild is a software build and installation framework
>  written in Python that allows you to install software in a structured,
>  repeatable and robust way. - Homepage: http://hpcugent.github.com/
> easybuild/
>     }
> }
>
> module-whatis {Description: EasyBuild is a software build and installation
> framework
>  written in Python that allows you to install software in a structured,
>  repeatable and robust way. - Homepage: http://hpcugent.github.com/
> easybuild/}
>
> set root /path/to/easybuild-framework
>
> conflict EasyBuild
>
> prepend-path    PATH                    $root
> setenv  EBROOTEASYBUILD                 "$root"
> setenv  EBVERSIONEASYBUILD              "dev"
>
> prepend-path    PYTHONPATH              $root
> prepend-path    PYTHONPATH              $root/../easybuild-easyblocks
> prepend-path    PYTHONPATH              $root/../easybuild-easyconfigs
> prepend-path    PYTHONPATH              $root/../vsc-base/lib
>
> Damian
>
> On 05/04/17 19:07, "[email protected] on behalf of Kenneth
> Hoste" <[email protected] on behalf of
> [email protected]> wrote:
>
>     On 05/04/2017 07:59, Åke Sandgren wrote:
>     > Install the bootstrap in a temp dir, mod load it, install the version
>     > you want in the proper place, drop the temp.
>
>     This is indeed the only way for now, the bootstrap script doesn't
>     support specifying a particular version to install.
>
>     If there's enough demand for it, we could, but since you can just
>     temporarily use the latest EasyBuild version to install an older
> version
>     as Åke suggested, I don't see much value in it to be honest...
>
>     Without the bootstrap script, you could also just use 'easy_install' or
>     'pip install', both of which support specifying specific versions, but
>     you wouldn't get an EasyBuild module to load then of course.
>
>
>     regards,
>
>     Kenneth
>     >
>     > On 04/05/2017 12:47 AM, Pieter Neerincx wrote:
>     >> Hi all,
>     >>
>     >> I'm familiar with the bootstrap script for EasyBuild and it does a
> very nice job when I want to get the latest and greatest EasyBuild deployed
> on a bare / plain vanilla server, but I cannot find an option to tell the
> bootstrap script to install a specific version... and sometimes this comes
> in handy when you want to reproduce an environment with the risk of running
> into new bugs or backwards incompatible features ;).
>     >>
>     >> When deploying a tool with EasyBuild itself it's easy to request a
> specific version, but how do I do that for EasyBuild (when there is not
> already another EasyBuild on the system)?
>     >>
>     >> Cheers,
>     >>
>     >> Pieter
>     >>
>     >>
>     >> -------------------------------------------------------------
>     >> phone: +31 6 143 66 783
>     >> e-mail: [email protected]
>     >> skype:  pieter.online
>     >> -------------------------------------------------------------
>     >>
>
>
>
>
>
> ------------------------------------------------------------
> ------------------------------------
> ------------------------------------------------------------
> ------------------------------------
> Forschungszentrum Juelich GmbH
> 52425 Juelich
> Sitz der Gesellschaft: Juelich
> Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
> Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
> Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender),
> Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
> Prof. Dr. Sebastian M. Schmidt
> ------------------------------------------------------------
> ------------------------------------
> ------------------------------------------------------------
> ------------------------------------
>
>


-- 
Pablo Escobar López
HPC systems engineer
sciCORE, University of Basel
SIB Swiss Institute of Bioinformatics
http://scicore.unibas.ch

Reply via email to