Search Criteria
Package Details: lmod 8.4.24-1
| Git Clone URL: | https://aur.archlinux.org/lmod.git (read-only, click to copy) |
|---|---|
| Package Base: | lmod |
| Description: | Environment modules system based on Lua that handles MODULEPATH hierarchical problem. Supports also legacy TCL modules |
| Upstream URL: | https://github.com/TACC/Lmod |
| Licenses: | |
| Conflicts: | |
| Provides: | |
| Submitter: | wookietreiber |
| Maintainer: | matse |
| Last Packager: | matse |
| Votes: | 4 |
| Popularity: | 0.000004 |
| First Submitted: | 2017-01-17 13:22 |
| Last Updated: | 2021-02-24 18:39 |
Dependencies (7)
- bash (bash-devel-git, bash-devel-static-git)
- lua-filesystem
- lua-posix (lua-posix-git)
- procps-ng (procps-ng-git, procps-ng-static, procps-ng-nosystemd-minimal-git, procps-ng-nosystemd)
- tcl (tcl85, tcl-nothreading)
- tcsh (optional) – supported shell
- zsh (zsh-git, zsh-athame-git, zsh-fix-winchanged-git, zsh-minimal-git) (optional) – supported shell
Latest Comments
1 2 3 Next › Last »
matse commented on 2020-09-04 17:23
@berquist: Updated to newest release and done. Thanks for the hint.
berquist commented on 2020-09-04 02:43
Can you change
env-modules-tcltoenv-modulesinprovidesandconflicts?matse commented on 2020-08-06 10:28
@simonp yes, it's because of the update to lua 5.4 and broken lua-posix at the moment. Since the package was updated today, just reinstall / recompile lua-posix and it will work again.
lahwaacz commented on 2020-08-06 10:14
@simonp: you need to rebuild all lua modules and this package for the new lua version.
simonp commented on 2020-08-06 09:32
I'm getting the following error after updating lua this morning:
/usr/bin/lua: version mismatch: app. needs 503.0, Lua core provides 504.0 stack traceback: [C]: in ? [C]: in function 'require' /usr/share/lua/5.3/posix/init.lua:23: in main chunk [C]: in function 'require' /usr/share/lmod/lmod/libexec/lmod:61: in main chunk [C]: in ?
matse commented on 2019-06-19 23:23
lahwaacz: Convinced and thanks for the information! Fixed!
lahwaacz commented on 2019-06-19 05:34
matse: The assumption is for the base-devel group, not for base - see e.g. https://bbs.archlinux.org/viewtopic.php?pid=1699678#p1699678. The wiki was wrong, I just fixed that.
matse commented on 2019-06-18 23:11
lahwaacz: procps-ng belongs to the base group, which is assumed to be installed on systems, on which you build your own packages, see: https://wiki.archlinux.org/index.php/Makepkg#Usage
lahwaacz commented on 2019-06-18 20:09
It does not seem to build in a clean chroot unless I add
procps-nginto depends.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 "modules.sh". 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 https://wiki.archlinux.org/index.php/Zsh#Startup/Shutdown_files) to source /etc/profile which again sources all *.sh files in /etc/profile.d where "modules.sh" gets sourced and inits lmod via the zsh file. So placing modules.sh in /etc/profile.d and renaming the zsh file to zsh.sh and place it there, is not, how it is intended to load lmod.