On Wed, Jan 22, 2014 at 2:44 AM, Andreas Tille <[email protected]> wrote:
> Hi Yaroslav, > > On Tue, Jan 21, 2014 at 11:39:54PM -0500, Yaroslav Halchenko wrote: > > I have ran into Luis's recent blog post > > http://www.osehra.org/blog/backporting-fis-gtm-ubuntu-linux-distribution > > > > Environment Set Up > > Setting up the usual environment variables in the bash shell: > > export gtm_dist='/usr/lib/fis-gtm/V6.0-003-2~nd12.10_x86_64' # > backported from NeuroDebian > > export gtmgbldir=$HOME/data/gtm/database > > export gtmroutines="$HOME/data/gtm/o($HOME/data/gtm/r) > $gtm_dist/libgtmutil.so $gtm_dist" > > > > > > Now that Alastair has packaged environment-modules we could start using > them I > > think, and then in your case it should then be just a matter of > > > > module load fis-gtm > > > > which would set all those environments. > > Sounds good. > > Yes, This looks great. We will appreciate anything that will reduce the barrier of entry for learning M/MUMPS. Certainly the need for setting those environment variables (although not particularly difficult) is just one more opportunity for typos, mistakes and things going wrong, which can lead to a first visitor to M / MUMPS to have a frustrating experience. I know that I have run in trouble many times due to simple errors in those environment variables. It is great that they considered the case of having multiple version installed of the same tools. Which is one of the scenarios that Bhaskar has been very keen to make sure that are supported. This will also be very useful for the VistA package. Since it will also enable to have multiple installations running side by side. So, how do we start using the environment-modules ? (I apologize, if I missed it from your link to the email thread). Could you suggest an example that we could follow ? Thanks Luis
