Upstream software project

modules

Change environment at runtime

About modules

Change environment at runtime

This project links 7 native package records across 5 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; openSUSE Leap 15.6: 1 package records; openSUSE Leap 16.0: 2 package records; openSUSE Tumbleweed: 2 package records. Catalog coverage diagram, not an application screenshot.modules: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsopenSUSE Leap 15.61 recordsopenSUSE Leap 16.02 recordsopenSUSE Tumbleweed2 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
modules
Publisher
Not authoritatively mapped
Native package records
7
Operating systems
debian-12, debian-13, opensuse-leap-15-6, opensuse-leap-16-0, opensuse-tumbleweed
License expression
GPL-2.0-or-later
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

The Modules package is a tool that simplify shell initialization and lets users easily modify their environment during the session with modulefiles. Each modulefile contains the information needed to configure the shell for an application. Once the Modules package is initialized, the environment can be modified on a per-module basis using the module command which interprets modulefiles. Typically modulefiles instruct the module command to alter or set shell environment variables such as PATH, MANPATH, etc. modulefiles may be shared by many users on a system and users may have their own collection to supplement or replace the shared modulefiles. Modules can be loaded and unloaded dynamically and atomically, in an clean fashion. All popular shells are supported, including bash, ksh, zsh, sh, csh, tcsh, fish, as well as some scripting languages such as tcl, perl, python, ruby, cmake and r. Modules are useful in managing different versions of applications. Modules can also be bundled into metamodules that will load an entire suite of different applications.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. Package environment-modules

    bookworm (Debian 12 (Bookworm)) (devel): Modular system for handling environment variables

    5.2.0-1: amd64 arm64

    Source: modules

Debian 13 (Trixie)

  1. Package environment-modules

    trixie (Debian 13 (Trixie)) (devel): Modular system for handling environment variables

    5.5.0-1: amd64 arm64

    Source: modules

openSUSE Leap 15.6

  1. Package Modules

    leap-15.6 (openSUSE Leap 15.6) (System/Management): Environment Modules

    3.2.10-1.29: aarch64 ppc64le s390x x86_64

    Source: Modules

openSUSE Leap 16.0

  1. Package Modules

    leap-16.0 (openSUSE Leap 16.0) (System/Management): Change environment at runtime

    4.8.0-160000.2.2: aarch64 ppc64le s390x x86_64

    Source: Modules

  2. Package Modules-doc

    leap-16.0 (openSUSE Leap 16.0) (Documentation/Other): Documentation for Environment Modules

    4.8.0-160000.2.2: noarch

    Source: Modules

openSUSE Tumbleweed

  1. Package Modules

    tumbleweed (openSUSE Tumbleweed) (System/Management): Change environment at runtime

    4.8.0-4.6: x86_64

    Source: Modules

  2. Package Modules-doc

    tumbleweed (openSUSE Tumbleweed) (Documentation/Other): Documentation for Environment Modules

    4.8.0-4.6: noarch

    Source: Modules

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.