BTW: In production HPC environments similar configurations are deployed, I've done so in a few different installations (plus a few other neat hacks for usability).
I don't see why someone that installs lmod by choice wouldn't want them. I've just been conservative w.r.t. automatically setting lmod up for the user. Aaron On Mon, Nov 21, 2016 at 4:39 AM, Aaron Zauner <a...@azet.org> wrote: > Sorry for the late reply. > > Thanks for working on this. I'm fine with the changes you've made. Haven't > tested to be honest as I had limited time since you've worked on these > changes to do so. > > Again thanks for updating, > Aaron > > On Fri, Nov 11, 2016 at 11:57 PM, Ana Guerrero Lopez <a...@debian.org> > wrote: > >> Control: tags 793355 + patch >> Control: tags 793355 + pending >> >> Dear maintainer, >> >> I've prepared an NMU for lmod (versioned as 6.6-0.1) and uploaded it >> to DELAYED/10. This means in 10 days my package will be automatically >> uploaded to the archive unless you upload a package yourself or >> ask me to remove the package from the delayed queue. >> >> I'm doing the NMU because it would be a pity to release Stretch with an >> old version of lmod. Since you're maintaining the package in github, >> I forked your repository and you can see easily my changes at: >> https://github.com/ana/lmod-deb >> >> Please, take a look, some of my changes are quite intrusive since I >> made some changes to have lmod behaving like environment-modules: >> - MODULEPATH can be set in a file /etc/lmod/modulespath >> - added /etc/profile.d/lmod.sh so /usr/share/lmod/lmod/init/$SHELL >> is automatically run. >> >> Best regards, >> Ana >> > >
