fyi. -------- Original Message -------- Subject: Re: [easybuild] module search & module install: CHECK List-Post: [email protected] Date: Sun, 19 Aug 2012 11:52:49 +0200 From: Fotis Georgatos <[email protected]> Organization: CERN/NTUA To: Kenneth Hoste <[email protected]>
Hi Kenneth, On 19/08/2012 11:29, Kenneth Hoste wrote: > Nice, great tricks! Please document this somewhere on your EasyBuild wiki, and > open an issue to pull it in at the main wiki. Done: https://github.com/fgeorgatos/easybuild.experimental/wiki/Module-command-extension-in-bashrc > Because according to module function you redefine in .bashrc, the install > requires a 2nd argument, but your example doesn't use any? I am not sure I get you: shift does a "left shift" on the operands, while $@ takes all the params. (ok, "search" should also become more intelligent for multiple operations...) > BTW: a similar, but more advanced, feature is being added to EasyBuild, that > allow you to just specify a software name (and optionally version and > toolkit), and then EasyBuild will try it's very best to find (and optinally > tweak) an easyconfig that can be used to build what's requested. > (see https://github.com/boegel/easybuild/tree/318-change-toolkit, it's not > finished yet though) In fact, that's something I had in mind, too: It *is* better to pass down the search to a similar function in easybuild, because with an '--investigate' parameter it could even go as far as checking osdependencies and what have you with CUDF and so on and come up with a build proposal plan. The options are unlimited here... -- echo "sysadmin know better bash than english" | sed s/min/mins/ \ | sed 's/better bash/bash better/' # Yelling in a CERN forum
