Changes between Version 21 and Version 22 of Admin/StandardOperatingProcedures/InstallSoftwareFromSource

Timestamp:

Oct 18, 2019, 2:04:15 PM (5 years ago)

Author:

ausa0001

Comment:

--

Admin/StandardOperatingProcedures/InstallSoftwareFromSource

@@ -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.
   1. Write a module file (copy and edit previous version or so) 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 (or SOFTWARE/VERSION.lua if you prefer to write a Lua module). See below for special routines for installing Python packages and Perl packages.
-  1. Add the module file to subversion with `svn add` (you might have to add the directory too, if you had to create it) and then commit the module file with 'svn commit'.
+  1. Add the module file to subversion with `svn add` (you might have to add the directory too, if you had to create it) and then commit the module file with `svn commit`.
   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.
   1. Document any deviations from the documented install procedure of the software in the ticket.