Package Details: lmod 8.1.7-1

Git Clone URL: (read-only)
Package Base: lmod
Description: Environment modules system based on Lua that handles MODULEPATH hierarchical problem. Supports also legacy TCL modules
Upstream URL:
Licenses: custom
Conflicts: env-modules-tcl, lmod-git
Provides: env-modules-tcl
Submitter: wookietreiber
Maintainer: matse
Last Packager: matse
Votes: 4
Popularity: 0.068810
First Submitted: 2017-01-17 13:22
Last Updated: 2019-06-12 05:50

Dependencies (6)

Required by (4)

Sources (1)

Latest Comments

1 2 Next › Last »

matse commented on 2019-05-24 05:35

berquist: zsh support has not been removed, I myself use it. The supposed way to init lmod on zsh is also with "". There in line 71 the shell specific file gets loaded. The file "/usr/share/lmod/lmod/init/zsh" was never meant to land in "/etc/profile.d". By default zsh users don't have to do anything, because the arch default on zsh is (see to source /etc/profile which again sources all *.sh files in /etc/profile.d where "" gets sourced and inits lmod via the zsh file. So placing in /etc/profile.d and renaming the zsh file to and place it there, is not, how it is intended to load lmod.

berquist commented on 2019-05-23 23:48

Why did you remove ln -sf /usr/share/lmod/lmod/init/zsh modules.zsh? Z shell support still exists.

angelv commented on 2018-07-04 10:15

On upgrade, I got:

error: failed to commit transaction (conflicting files) lmod: /usr/share/lmod/lmod exists in filesystem

I just rm /usr/share/lmod/lmod and did the package install again.

wookietreiber commented on 2018-06-11 17:12

@simonp: done

simonp commented on 2018-06-11 06:28

there is a conflict with env-modules-tcl (AUR):

lmod: /usr/share/man/man1/module.1.gz exists in filesystem (owned by env-modules-tcl)

devzero commented on 2018-04-19 06:10

I see you changed make pre-install to make install, that solved the problem for me.

wookietreiber commented on 2018-04-18 19:28

I don't quite get what the problem is.

The package is creating the /usr/share/lmod/lmod symlink to the version it installs, as is normal with lmod. Then it creates the profile.d symlinks, e.g. /etc/profile.d/ -> /usr/share/lmod/lmod/init/profile.

I just did a fresh install, started a new login shell (bash) and it works.

At which point are your symlinks broken?

Edit: Sorry, forgot to mention, that I used the new PKGBUILD I just pushed.

devzero commented on 2018-04-18 01:26

Even with the pre-install step in, the package is still installing under /usr/share/lmod/$pkgver instead of /usr/share/lmod/lmod:

$ pacman -Qql lmod | xargs -n1 dirname | sort -u

This breaks the symlinks in /etc/profile.d, and even if they pointed to the right place, the shell init scripts all have /usr/share/lmod/lmod hardcoded, so they still wouldn't work.

I am able to work around this by symlinking /usr/share/lmod/$pkgver to /usr/share/lmod/lmod, but it's not ideal.

Ergo commented on 2017-09-28 14:42

Thank you very much! But there is "pre-install" now instead of just "install", so the package doesn't work out of the box because the links are not created in the path.

wookietreiber commented on 2017-09-28 12:45

just updated.