Package Details: lmod 7.7.29-1

Git Clone URL: https://aur.archlinux.org/lmod.git (read-only)
Package Base: lmod
Description: environment modules system based on Lua, supports legacy TCL modules
Upstream URL: http://lmod.readthedocs.org
Licenses: custom
Conflicts: env-modules-tcl, lmod-git
Provides: env-modules-tcl
Submitter: wookietreiber
Maintainer: wookietreiber
Last Packager: wookietreiber
Votes: 4
Popularity: 0.215102
First Submitted: 2017-01-17 13:22
Last Updated: 2018-06-11 17:11

Dependencies (6)

Required by (3)

Sources (1)

Latest Comments

1 2 Next › Last »

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/modules.sh -> /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
/
/etc
/etc/profile.d
/usr
/usr/share
/usr/share/licenses
/usr/share/licenses/lmod
/usr/share/lmod
/usr/share/lmod/7.7.3
/usr/share/lmod/7.7.3/init
/usr/share/lmod/7.7.3/lib
/usr/share/lmod/7.7.3/libexec
/usr/share/lmod/7.7.3/libexec/term
/usr/share/lmod/7.7.3/lib/term
/usr/share/lmod/7.7.3/messageDir
/usr/share/lmod/7.7.3/modulefiles
/usr/share/lmod/7.7.3/modulefiles/Core
/usr/share/lmod/7.7.3/modulefiles/Core/lmod
/usr/share/lmod/7.7.3/modulefiles/Core/settarg
/usr/share/lmod/7.7.3/settarg
/usr/share/lmod/7.7.3/shells
/usr/share/lmod/7.7.3/tools
/usr/share/lmod/7.7.3/tools/i18n
/usr/share/man
/usr/share/man/man1

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.

Ergo commented on 2017-09-28 12:03

Hi:
The package is out of date. I updated the aur repository locally to version 7.7 (it is really very simple) and it is working in my system very fine. So if you want my changes just ask. Best

wookietreiber commented on 2017-02-05 17:00

The **module** command is provided as a shell function via the `/etc/profile.d` scripts. If you source them or start a new login shell and type:

```
$ type module
module is a function
module ()
{
eval $($LMOD_CMD bash "$@") && eval $(${LMOD_SETTARG_CMD:-:} -s sh)
}
```