Changes between Version 29 and Version 30 of Admin/StandardOperatingProcedures/InstallSoftwareFromSource
- Timestamp:
- May 19, 2021, 2:15:34 PM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Admin/StandardOperatingProcedures/InstallSoftwareFromSource
v29 v30 19 19 1. Install package into the the folder obtained at step 4. (This should be done as your ordinary user, in a shell where you have run the `gridsw` command.) If the install script/makefile/install procedure complains about denied permissions, DO NOT USE SUDO. You should rather check that all install paths etc are correct. 20 20 1. Write a module file (or copy and edit previous version) to reflect the new software version you have installed. The module file should be created in **/opt/modulefiles_staging/Core** for standard software and named SOFTWARE/VERSION.lua. See below for special routines for installing Python packages and Perl packages. 21 1. Add the module file to subversion with `svn add software/version.lua`. If this is the first version installed of the software, you also need to add the directory to Subversion (`svn add /opt/modulefiles_staging/Core/software/ version/`). Once the file (and directory are added), commit the module file with `svn commit software`.21 1. Add the module file to subversion with `svn add software/version.lua`. If this is the first version installed of the software, you also need to add the directory to Subversion (`svn add /opt/modulefiles_staging/Core/software/`). Once the file (and directory are added), commit the module file with `svn commit software`. 22 22 1. Update the wiki page for the software referenced from the software index found on [[Software]] (or create a new one). This page should, as a bare minimum, contain any local modifications or specifics, and a link to a manual for the software. If you need to create a new page, please use the software page template. 23 23 1. Document any deviations from the documented install procedure of the software in the ticket.