Hi Fokko, this resonates well with another idea I had the other day: * store the modulefile as a complex python struct (dict?) and dump it in JSON or yaml. Existing directory ./easybuild would be a good place for such business. That would permit, from then on, a zillion other things with minimal effort. Hint: existing modulefiles contain conditional statements, that must be handled somehow. There are some more features to consider, such as header/footer.
Anyway, this is just an idea, probably good hackathon subject. cheers, Fotis On May 12, 2015, at 11:45 AM, Fokko Masselink <[email protected]> wrote: > Hi Kenneth, > > I was looking into providing a HMS structure next to the one we already have > (a flat one, the default). > So I was just trying to see what works and what doesn't. > I'll take your notes into account. > > Would it be an idea to have a plain file (app-version.mod) somewhere after a > real install in the installdirectory/easybuild (which is already used for the > logfiles and a copy of the eb-file) that only holds the various sections for > the modulefile, like the setenv, prepend/append-path statement etc and then > when you rebuild modulefile that file is taken as the basis to regenerate > them? > That way you have all the information to rebuild the modulefile, though not > have to go through the whole install process again? > Just a thought... > > I can imagine if you guys have more pressing issues than this one. As said, > I'm trying to see what is possible. Not migrate. And if I want to I could use > your wrapper suggestion. > > kind regards, > Fokko cheers, Fotis -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # signal detected in a CERN forum
