{"id":23544310,"url":"https://github.com/abrodkin/modules","last_synced_at":"2025-10-24T08:57:00.347Z","repository":{"id":27087980,"uuid":"30555006","full_name":"abrodkin/modules","owner":"abrodkin","description":"Environment Modules","archived":false,"fork":false,"pushed_at":"2015-02-18T11:13:05.000Z","size":4960,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"master","last_synced_at":"2025-05-15T08:45:08.809Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"http://modules.sourceforge.net/","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/abrodkin.png","metadata":{"files":{"readme":"README","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.GPL","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2015-02-09T19:50:28.000Z","updated_at":"2015-02-24T07:34:58.000Z","dependencies_parsed_at":"2022-09-02T04:50:21.910Z","dependency_job_id":null,"html_url":"https://github.com/abrodkin/modules","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/abrodkin/modules","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/abrodkin%2Fmodules","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/abrodkin%2Fmodules/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/abrodkin%2Fmodules/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/abrodkin%2Fmodules/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/abrodkin","download_url":"https://codeload.github.com/abrodkin/modules/tar.gz/refs/heads/master","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/abrodkin%2Fmodules/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":261558827,"owners_count":23177098,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-12-26T07:14:52.517Z","updated_at":"2025-10-24T08:57:00.263Z","avatar_url":"https://github.com/abrodkin.png","language":"C","readme":"\n                             The Modules Package\n                                Version 3.1\n                                \n                               John L. Furlan\n                               jlf@behere.com\n\n\t\t\t        Peter W. Osel\n                                 pwo@Osel.DE\n\n                                Jens  Hamisch\n                          Jens.Hamisch@Strawberry.COM\n\n                                  R.K. Owen\n                              rk@owen.sj.ca.us\n\n\n                               2  October 1996\n                                2  June 2000\n\n1. Introduction\n_______________\n\nThis directory contains a copy of The Modules Package that uses Tcl (Tool\nCommand Language) developed by John Ousterhout at Sun Microsystems.  You\nmust obtain a copy of Tcl (at least version 8.3).  Tcl should be available\neither at the same site you obtained The Modules Package or from\nhttp://dev.scriptics.com/ .\n\nFor an introduction to The Modules Package, see the paper, \"Modules: Providing\na Flexible User Environment\", in the Proceeding of the 1991 Large Installation\nSystems Administrators USENIX Conference (USENIX LISA V).  A copy of the paper\nis included in Postscript form in doc/Modules-Paper.ps.  The paper describes\nthe concepts behind Modules and a prototype/proof-of-concept implementation\nbased on shell scripts being sourced into the user environment.  The\nimplementation details have changed, but the package concepts haven't.\n\n\n2. Documentation\n________________\n\nThe ./doc directory contains both the paper and man pages describing the\nuser's and the module writer's usage.\nLook at ChangeLog for detailed information regarding changes.\n\nBig changes to 3.2:\n    o  Using the automake/autoconf mechanism for creating the configure script.\n\n    o  Have the configure script test and set more things with regards to\n       /bin/sh and /bin/csh characterstics.\n\n    o  Lots of code clean-up.\n\n    o  Made the tests conditional on configure options.\n\n    o  Handle the silent changes in Tcl 8.4\n\nBig changes to 3.1:\n    o  Changed the license to GPL\n\n    o  Source code cross-referencing documented in ./xref/*.html files.\n\nBig changes since 3.0 prior to 3.1:\n    o  Ported to Linux.\n\n    o  Removed any dependence on low-level Tcl routines.\n\n    o  Can use environment variable references in MODULEPATH for indirection.\n\n    o  Can switch between different versions of the module command.\n\n    o  Fixed \"module whatis\" to work as advertised.\n\n    o  Added the INSTALL document to aid in first-time and upgrading\n       installations.\n\n    o  Fixed \"module avail\" and \"module list\" to show levels deeper than 2.\n\n    o  Added \"is-loaded\" and \"module-info specified\" to modulefile commands.\n\nBig changes for 3.0:\n    o  Testsuite added\n\n    o  Support for Tcl/TclX 7.6 and Tk 4.2\n\n    o  Introduction of user levels for generation of error messages\n\n    o  Enhanced module logging facilities using stdout, stderr, files\n       and the syslog\n\n    o  Enhanced module trace feature\n\n    o  Modulefile configuration management. Symbolic module file names\n       and aliases\n\n    o  Hierarchical modulecmd rc-file structure\n\n    o  Command line switches\n\n    o  Traceable output for module list and module command (configurable\n       and on request)\n\n    o  Active dependecy resolution. This is experimental at the moment!!!\n\nBig changes for 2.3:\n    o  Support for Tcl/TclX 7.5 and Tk 4.1\n\n    o  Code cleanup. Added inline documentation. Unification of source\n        module layouts.\n\n    o  Added alloc tracer for locating memory leaks\n\n    o  Added 'uname domain'.\n\n    o  Added M_HELP as a modetype, so that 'module-info mode [help]' will\n\tbe possible\n\n    o  Optional support for extended Tcl (tclX) 7.x\n\n    o  Modules now uses the standard Tcl initialization (init.tcl),\n\tenabling autoloading of Tcl functions.\n\nBig changes for 2.2:\n    o  Installation changed to use GNU's configure script (version 2.x).\n\n    o  Updated to support Tcl 7.x\n\n    o  Paths and modulefile names with '+'s in them should work now.\n\n    o  Multi-level paths should work.  Well, at least better than 2.0.\n\n    o  \"module load .\" doesn't dump core.\n\n    o  Support for \"perl\" output.\n\n    o  Ability to exit without having modulefile listed as \"loaded\".\n        Use an argument to exit other than 0 or 1.\n\n    o  More stringent checking of user-level command names.\n\n    o  A sysconf.h file to help with multi-platform support.\n        This area and the installation process still needs work.\n\n    o  A new and improved cmdXResource.c\n\n    \nBig changes for 2.0:\n\n    o  Added a new environment variable, _LOADED_MODULEFILES_, which keeps\n        track of which file and directory each modulefile was loaded from.\n        This is necessary for locating modulefiles if the MODULEPATH variable\n        has changed or if a full pathname was specified as the modulefile to\n        load.\n\n    o  Added an update sub-command which attempts to reload all of the\n        currently loaded modulefiles.  When Modules is first initialized a\n        snapshot of the environment is saved into a file in the user's home\n        directory.  When the update sub-command is run, the environment\n        variables are restored to their earlier state and the modulefiles are\n        reloaded.  Only the variables that modulefiles touch are changed.\n        \n    o  Added an purge sub-command which unloads all currently loaded\n        modulefiles.\n    \n    o  set-alias should be fixed and should work for all shell types.  In the\n        case of the Bourne shell-variants, it creates functions.\n\n    o  If multiple modulefiles are listed to be added or removed and one of\n        them has an error, only that modulefile will fail.  All of the other\n        modulefiles will load or unload successfully (assuming they don't in\n        turn have errors).\n\n    o  INCOMPATABILITY ISSUE:  stdout is not tied to stderr any more.  So, if\n        you to a 'puts stdout' in any of your modulefiles, that will go\n        directly to the shell.  You should change all puts statements that\n        goto stdout to goto stderr.\n        \n    o  avail prints out all of the modulefiles by recursively looking through\n        all directories under every entry in MODULEPATH.\n        Only files containing the \"#%Module\" magic cookie\n        header and that don't end in '~' will be listed.  Other files will be\n        ignored.\n\n    o  A .version file in a modulefile directory will be parsed to find out\n        which modulefile is the default version for the directory name.\n\n    o  Locating modulefiles is recursive and ignores files ending in '~' and\n        which don't have the \"#%Module\" magic header.\n\n    o  The switch command really works now.\n\n    o  Added uname command for fast access to system information.  Not sure if\n        uname is portable.\n\n    o  Unload using a directoryname will look for a version that is already\n        loaded instead of the default version specified by the .version file\n        or by the highest lexicographical name in the directory.\n\n    o  Added ability for modulefile-specific help and modulefile-specific\n        display.\n\n\n\n3. Building and Installing Modules\n__________________________________\n(Read the INSTALL file for a more recent description of installation\nprocedures.)\n\nFirst, you'll need to decide on a location to keep Modules on your network.\n\nThe path name to the initialization files must be the same on all of the\nsystems using Modules.  This is because your users' .cshrc or other shell\nstartup files must hard code this directory in order to source their Modules\ninitialization file.\n\nYou will also need to choose a location for the 'modulecmd' program and all of\nyour modulefiles.  The location of these can be different on different\nsystems, but it is not recommended.  These paths are used in the Modules\ninitialization files.  If you decide not to use this structure, then you\nwill need to edit the initialization files by hand.  Use the --prefix\nconfigure option to control the installation of Modules.  See below for more\nconfigure options.\n\nExample:\n\tIf you decide to keep Modules in /depot/Modules, run\n            \"configure --prefix=/depot/Modules\" \n\n\tinitialization file   --\u003e  /depot/Modules/init\n\tmodulefiles           --\u003e  /depot/Modules/modulefiles\n\tmodulecmd             --\u003e  /depot/Modules/bin\n \tmanual pages          --\u003e  /depot/Modules/man\n \tTcl libraries\t      --\u003e  /depot/Modules/lib/tcl\t(if any)\n\nThe Modules Package is written in conformant ANSI C and should build on any\nUNIX machine with an ANSI C compiler like the GNU C compiler.  Check the\nMACHINES file for a list of machines and OSs Modules has been test built on.\nThe module error logger requires the ANSI C 'stdarg.h' being installed. At\nthe moment there's no support for traditional vargargs handling using \n'varargs.h'.\n\nTo build Modules, first build Tcl and run the tests provided with Tcl to\nverify it built correctly.\n\nIf you want to use the testsuite, you should install dejagnu-1.2 or better\nbefore configuring modules. Be sure to have your PATH pointing to 'runtest'\nwhen calling 'configure'.\n\nThen run the GNU autoconf script, ./configure.\nA Makefile will be automatically generated.\n\nSome Modules-specific configure options...  (See also ./configure --help)\n\nAutoconf @variable@'s can be passed along to the configure script, in\nparticular for setting paths.  The one of interest is @VERSION@ for\nusing the current module version. e.g.  --prefix=/usr/local/Modules/@VERSION@\n\n------------------------------------------------------------------------\n    --with-etc-path=\u003cpath\u003e      use etc path=\u003cpath\u003e\t\t[/etc]\n    --with-skel-path=\u003cpath\u003e     use skel path=\u003cpath\u003e\t\t[/etc/skel]\n\n  o Place to find the csh.modules * profile.modules files and where\n    the new user dot files are (both are needed by add.modules script).\n  o The skeleton user dot files need to point to the etc path for\n    setting up modules environment on login.\n\n------------------------------------------------------------------------\n    --with-split-size=\u003csize\u003e\tWith split size=\u003csize\u003e\t\t[TEST]\n    --without-split-size\tWithout  - \" -\n\n  o Most C Shell implementations have a size requirement on the length of\n      the line which can be evaluated.  If you run into very long\n      environment changes, you may run into this problem.  Select size\n      to be something less than the size your C Shell will accept.\n      The configure script will test this in your /bin/csh upto\n      10,000 characters.  If you do not specify anything configure\n      will set the split-size for you if the limit it finds is less\n      than 4000 characters.  This can be overridden by specifying\n      --with-split-size='some_value' specifying --without-split-size\n      will disable this feature.  Just specifying --with-split-size\n      without a value will default to a value of 1000.\n\n------------------------------------------------------------------------\n    --enable-shell-funcs\tWith sh functions\t\t[TEST]\n    --disable-shell-funcs\tWithout  - \" -\n\n  o Does your Bourne Shell support functions?  If so, then the modulefile\n      set-alias will work properly.  If not, aliases will not be available\n      when using the Bourne Shell.\n      The default is to test your /bin/sh when configuring build, but\n      specifying either option will override the tested characteristic.\n\n------------------------------------------------------------------------\n    --enable-shell-alias\tWith sh functions\t\t[TEST]\n    --disable-shell-alias\tWithout  - \" -\n\n  o Does your Bourne Shell support aliases?  A true Bourne Shell doesn't\n      but most are just a link to some other Bourne-like shell.  If so,\n      then modules will use the alias mechanism when using set-alias.\n      If not, aliases will not be available unless sh functions are\n      supported when using the Bourne Shell.\n      The default is to test your /bin/sh when configuring build, but\n      specifying either option will override the tested characteristic.\n\n------------------------------------------------------------------------\n    --enable-shell-eval\t\tWith shell alias eval\t\t[DEF]\n    --disable-shell-eval\tWithout  - \" -\n\n  o This specifies whether aliases will be evaluated by the shell or\n      sourced from a temporary file.  Some shells can't handle the\n      specification of aliases in the eval line very well.  To get around\n      this problem, when aliases are set by a modulefile, a temporary file\n      is created and then sourced into the shell.  This guarentees the\n      aliases are evaluated correctly, but may leave lots of cruft\n      in the /tmp directory, which is generally not a good idea.\n \n------------------------------------------------------------------------\n    --enable-free\t\tWith free() calls\n    --disable-free\t\tWithout  -\" -\t\t[DEF]\n\n  o Since the modulecmd is transient, disabling calls to free() can provide\n      some small performance enhancement since the memory usage is low and\n      the program will exit rapidly.  If you want the calls to free() back\n      in for some reason, set this option.\n\n------------------------------------------------------------------------\n     --with-static\t\tLink static (don't use dynamic libraries)\n     --without-static\t\tUse dynamic libraries\t\t[DEF]\n\n  o A note.  I've found that at least the X11 libraries should be linked\n      statically.  If you encounter problems, e.g. getting some warnings\n      about version mismatch of dynamic libraries, link the modulecmd\n      statically.\n\n  o If you're using Tcl/TclX 7.5 on an SunOS or Solaris box, the dynamic\n      loader library (libdl.so.1) will be liked in. Since this is not\n      available as a staic library, using  --without-static is recommended.\n\n------------------------------------------------------------------------\n     --with-tclx\t\tWith extended TCL (tclX) commands\n     --without-tclx\t\tWithout  - \" -\t\t\t[DEF]\n\n  o Extended Tcl is a superset of standard Tcl and is built alongside\n      the standard Tcl sources.  It adds many new commands to standard\n      Tcl, e.g. Unix Access Commands, File I/O Commands, String and\n      Character Manipulation Commands, ...  See the manual pages that\n      come with tclX for a complete list of added features.\n\n------------------------------------------------------------------------\n     --with-module-path=\u003cpath\u003e\tWith user defined MODULEPATH\n     --without-module-path\tDefault $prefix/modulefiles\t[DEF]\n\n  o Set the MODULEFILE environment variable in all initialization\n      files to the given \u003cpath\u003e (colon separated!).  The default\n      is to use $prefix/modulefiles (which usually contains version\n      specific modulefiles).\n  o Every site should use this to specify where local modulefiles\n      are placed which are independent of module versions.\n\n------------------------------------------------------------------------\n    --with-version-path         use module path=\u003cpath\u003e\n                                [/usr/local/Modules/versions]\n\n  o Place to put module version modulefiles for switching between different\n      versions of the module command.\n------------------------------------------------------------------------\n     --with-autoload-path=\u003cpath\u003e\tdirectories where Tcl will search\n\t\t\t\t\tfor libraries to load\n     --without-autoload-path\t\tDefault $prefix/lib/tcl\t[DEF]\n\n  o \u003cpath\u003e will be prepended to Tcl's auto_path variable.  These\n      directories are searched for library functions that can be\n      autoloaded.  Note that this path has to be *space* separated and\n      enclosed in double quotes!!\n      The default is to use \"$prefix/lib/tcl\".\n\n------------------------------------------------------------------------\n     --with-tcl=\u003cpath\u003e\t\tdirectory containting Tcl configuration\n\t\t\t\t(tclConfig.sh)\n     --with-tclx=\u003cpath\u003e\t\tdirectory containting TclX configuration\n\t\t\t\t(tclxConfig.sh)\n\n  o the tclConfig.sh file was created when Tcl was built, and has pointers\n  to where the libraries and header files were installed. It is usually\n  found in $prefix/lib, where $prefix is the directory you installed Tcl.\n  (Same for TclX too.)\n\n------------------------------------------------------------------------\n     --with-debug=\u003clevel\u003e\t\tSet up the debug level to the\n\t\t\t\t\tspecified value\n     --without-debug\t\t\tDisable debugging [DEF]\n\n  o The debug level will be set to the specified value. Available values\n      may be looked up in 'modules_def.h'. Debugging may be configured in\n      order to trace:\n\n\t- module commands\n\t- TCL interpreter initialization\n\t- callback functions\n\t- module file localization\n\t- utility functions\n\n      Enable this feature for debugging only! The higher the debugging level,\n      the greater the amount of runtime information printed! All debug mes-\n      sages will be spooled to \u003cstderr\u003e.\n\n      The debug-level cannot be changed at runtime at the moment! It is\n      configured as a fixed value at compile time!\n\n------------------------------------------------------------------------\n     --enable-version-magic             set .version magic requirement[DEF]\n     --disable-version-magic            unset requirement\n\n  o Enable or disable the requirement that .version files need the\n      \"#%MOdule1.0\" magic cookie at the file start to be properly recognized\n      and parsed.\n\n------------------------------------------------------------------------\nNO LONGER AVAILABLE\n     --enable-parseable-msgs\t\tConfigure parseable error messages\n     --disable-parseable-msgs\t\tUse the traditional ones\n\n  o Switch between traditional error messages in multi-line format or parse-\n      able ones that look like the GNU messages. The parseable message format\n      is:\n\n\tmodule(line):Message-Type:Message-Number: Text\n\n      with Message-Type being one of:\n\n\tINFO, WARNING, PROBLEM, ERROR, FATAL, PANIC, DEBUG\n\n      and an unique message id in decimal format.\n\n------------------------------------------------------------------------\n      --enable-logging                  Enable the module logging feature\n      --disable-logging                 No module logging [DEF]\n      --with-log-facility-verbose[=\u003cfacility\u003e] \n      --with-log-facility-info[=\u003cfacility\u003e]\n      --with-log-facility-debug[=\u003cfacility\u003e]\n      --with-log-facility-debug[=\u003cfacility\u003e]\n      --with-log-facility-warn[=\u003cfacility\u003e]\n      --with-log-facility-problem[=\u003cfacility\u003e]\n      --with-log-facility-problem[=\u003cfacility\u003e]\n      --with-log-facility-fatal[=\u003cfacility\u003e]\n      --with-log-facility-panic[=\u003cfacility\u003e]\n\n   o Turn logging on and define the logging facilities for the different\n     error levels. Each facility may be a syslog-facility as 'local7.debug',\n     a standard stream as 'stderr', a filename or the word 'no' for dis-\n     abling a single log facility.\n\n------------------------------------------------------------------------\n      --with-trace-load=\u003cvalue\u003e  \n      --with-trace-unload=\u003cvalue\u003e\n      --with-trace-switch=\u003cvalue\u003e\n      --with-trace-disp=\u003cvalue\u003e\n      --with-trace-list=\u003cvalue\u003e\n      --with-trace-avail=\u003cvalue\u003e\n      --with-trace-help=\u003cvalue\u003e\n      --with-trace-init=\u003cvalue\u003e\n      --with-trace-use=\u003cvalue\u003e\n      --with-trace-unuse=\u003cvalue\u003e\n      --with-trace-update=\u003cvalue\u003e\n      --with-trace-purge=\u003cvalue\u003e\n      --with-trace-clear=\u003cvalue\u003e\n      --with-trace-whatis=\u003cvalue\u003e\n      --with-trace-apropos=\u003cvalue\u003e\n\n   o Turns tracing for the specific module command on or off. The value\n     is a list of colon separated TCL regular expressions matching the\n     module files to be traced. This maybe overridden using the \n     'module-trace' command. See 'modulefile(4)' for detailed information.\n\n\n\nA number of example modulefiles have been provided  in the example-modulefiles\ndirectory.  This should help provide you with some idea on how to write\nmodulefiles.\n\nIf you upgrade from a previous module version and have adapted the\nMODULEPATH environment variable in your installed init files, don't\nforget to set the MODULEFILE in the configuration step:\n(See the INSTALL document for more current information.)\n \n\t./configure --with-module-path=$MODULEPATH\n\nJust type 'make' and it should build.\n\nIf you have dejagnu installed, you may want to run the testsuite now. Type\n'make check' and it should run.\n\nFinally, type 'make install' and 'modulecmd' along with the initfiles will be\ninstalled.\n\n\n4. modules-interest@lists.sourceforge.net\n_________________________________________\n\nAs of release 2.0, I have worked with Richard Elling to create a\nModules interest alias for discussion about Modules and other\nModules-related packages such as Richard's user-setup.\n\nThe email list was moved from eng.auburn.edu to SourceForge.net with\nversion 3.0.  If you would like to be added to the modules-interest alias,\nemail majordomo@lists.sourceforge.net with \"subscribe modules-interest\naddress\" in the body of the message where \"address\" is your Internet\ne-mail address.\n\n\n5. Miscellaneous\n________________\n\ntcsh(1) user might want to add the following to their tcsh startup file\n(~/.cshrc or ~/.tcshrc): \n\n# program tcsh's completion for module command:\ncomplete module \\\n\t'n/use/d/' \\\n\t'n/unuse/d/' \\\n\t'n/*/(load unload switch display avail use \\\n\t\tunuse update purge list clear help \\\n\t\tinitadd initrm initswitch initlist initclear)/'\n\n\nYou might want to add the following line to /etc/magic, so that file(1)\nrecognizes modulefiles:\n\n#\n# Environment Modules modulefiles\n#\n0\tstring\t\t#%Module1.0\tEnvironment Modules version 1.0\n\n\n6. Special Thanks\n_________________\n\nKen Manheimer and Don Libes at the National Institute of Standards and\nTechnology deserve special thanks for their help and ideas toward the\noriginal paper, design considerations, and the use of Tcl.\n\nMaureen Chew and others at Sun Microsystems have provided me with an\ntest site and many ideas on how to improve my Tcl implementation of\nModules.\n\nLeif Hedstrom added GNU's autoconf support, x-resource command, helped\nsignificantly with the port to Tcl 7.x and has provided valuable input.\n\nI would also like to thank Richard Elling at Auburn University for his \ncomments, help with the Modules' man pages and his application\n'user-setup'.  A paper on 'user-setup' was presented at this year's\nUSENIX LISA VI conference.  The paper and the application can be\nacquired via anonymous ftp from ftp.eng.auburn.edu.\n\nPeter W. Osel \u003cpwo@guug.de\u003e added support for Extended Tcl (TclX),\nautoloading of Tcl functions, autoconf 2.x;\n \nThere are many others that deserve thanks but too many to list here --\nthanks to everyone who has helped.\n\nR.K.Owen \u003crk@owen.sj.ca.us\u003e added the modules versioning, ported to Linux,\nreworked the code to use higher level Tcl calls eliminating the need for\nTcl internal header files, various code fixes and changes, added some useful\nscripts, and is the current maintainer of the modules-3.1 distribution.\n\nRobert Minsk \u003cegbert@centropolisfx.com\u003e, added the \"module-info specified\"\nand the \"is-loaded\" modulefile commands, and for various code and script\nfixes.\n\nFurther \u0026 updated list of contributors can be found in the ChangeLog file.\n\n\n7. Bugs and Comments\n____________________\n\nReport bugs to 'modules-interest@Eng.Auburn.EDU'.  Please try to provide\na full environment listing and a copy of the modulefiles you're trying\nto manipulate.  Be as explicit and detailed as possible.\n\nComments and suggestions for improvement are always welcome.\n\n\n8. Getting the Sources\n______________________\n\nThere are two ways to get the sources.  If you just intend to use\nmodules and have no interest in modifying or improving them, then\nget them via anonymous ftp from\n\nPrimary-site:\tftp1.sourceforge.net\t/pub/sourceforge/m/mo/modules\nAlternate-site:\tsunsite.unc.edu\t\t/pub/Linux/utils/shell/\nAlternate-site: owen.sj.ca.us\t\t/pub/rkowen/modules/\n\nHowever, if you have coding expertise and wish to contribute code\nmodifications ... or you want the ``bleeding edge'' latest sources\nthen get them via the Modules CVS repository server:\n\nThis will download the current checked-in version\n\n  cvs -d:pserver:anonymous@cvs.modules.sourceforge.net:/cvsroot/modules login\n        Just hit return when prompted for the password.\n\n  cvs -d:pserver:anonymous@cvs.modules.sourceforge.net:/cvsroot/modules \\\n\tcheckout modules \n\n(The preceeding commands may be wrong - visit \u003chttp://modules.sf.net\u003e for\nother CVS download instructions.)\n\nIf you have modules installed already from a recent distribution, then\nyou can use the aliases defined by the module-cvs modulefile.  Typically,\nit can be loaded with:\n\n  module load modules module-cvs\n\nThen use the modules-login and modules-get aliases.\n\nYou will need recent versions of automake and autoconf if you use the CVS\nversion of modules.\n\nAfter your initial checkout you must run the command:\n\n % autoreconf -f -i\n\nto generate the rest of the build infrastructure.\n\nFor a brief HOWTO on CVS read http://kooz.sj.ca.us/rkowen/howto/cvsF.html .\n\nTo contribute code patches, please \"cvs diff -u\" them against\nthe modules CVS repository.\n\n\nThanks,\nJohn L. Furlan\n(with additions by R.K.Owen and Harlan Stenn)\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fabrodkin%2Fmodules","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fabrodkin%2Fmodules","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fabrodkin%2Fmodules/lists"}