Command Line Installer (Linux Only)

The command line installer for the SCons Release Manager is located in the SCons-installer package in the CVS repository.  It is written in python and uses the same database interface as the GUI installer.

Purpose: Provide a command line interface to download and install release packages build by the SCons release manager.

Options and Parameters

-h, --help Print a short help message.
-c, --command Command to execute.
-o, --os Operating system to get the package for.
-p, --package Package to work with (ScienceTools, GlastRelease, etc.).
-v, --variant Variant of the built to get (Debug or Optimized).
-s, --version Version to get (09-17-00, 3104, etc.).
-t, --versionType Type of build to get (LATEST, HEAD, RELEASE).
-e, --extDir Location where external libraries are to be installed. Defaults to $GLAST_EXT.
-i, --instDir Location where the packages are to be installed. Default is the local directory.
-x, --extOnly Only install the external libraries.
-k, --pkgOnly Only install the packages; don't install the external libraries.
-d, --distribution Which distribution for the selected package to install (user, developer, or source)
-r, --pretend Don't actually install anything; just list the actions that would have been taken.
-f, --keepFiles Do not delete downloaded files once installation is complete.

Option Descriptions

-h, --help  
  Parameter that causes a short help message listing all available options to be printed to the screen
     
-c, --command <action>  
  Command to be executed by the script. The format is derived from the current CMT command line installer. Available possibilities for the value of <action> are listed below:
 
  • install
  • listOSes
  • listPackages
  • listVariants
  • listVersions
  • listVersionTypes
  • listDistributions
 Note: With the exception of the install action, all of these actions can be provided without any additional parameters. In that situation, a list of all the possible values for the option specified is given.
 

However, not all of the values may be available for the specific case the user is interested in. It is much more advisable to provide the necessary qualifying options to get specific information.

If not used without any options, each of the actions require additional options to be provided as described below:

Action

Required Options

listPackage - none -
listVersionTypes --package
listVersions --package, --versionType
listVariants --package, --versionType, --version
listOSes --package, --versionType, --version, --variant
listDistributions --package, --versionType, --version, --variant, --os
install --package, --versionType, --version, --variant, --os, --distribution

Option Descriptions (Continued):

-p, --package <name>
 

Package to work with (ScienceTools, GlastRelease, etc). This option is required for all later commands if specific information is desired or a package is to be installed. The current possible values for <name> are:

  • ScienceTools
  • GlastRelease
  • CHS
-t, --versionType <type>
 

Type of build you want to work with. Current possible values for <type> are:

  • Integration (can also use LATEST)
  • Release Candidate (can also use HEAD)
  • Release
-s, --version <version>
  Version of the software to get. This is the numeric part of the tag. For release builds it is of the form XX-YY-ZZ and for HEAD and LATEST builds it is simply a number.
-v, --variant <variant>
  Variant of the built to get. You only have two choices here: Debug and Optimized.
-o, --os <osname>
 

Option specifying the operating system we want the software for.

Since the release manager builds for a variety of different operating systems you need to specify the one you want. The exact OS choices is strongly dependent of the package, versionType, version and variant choices. Possible values of <osname> are:

  • redhat4-i686-32bit-gcc34
  • redhat4-x86_64-64bit-gcc34
  • redhat5-i686-32bit-gcc41
  • redhat3-i686-32bit-gcc32
  • tiger-i386-32bit-gcc40
  • Windows-i386-32bit-vc71
  • redhat5-x86_64-64bit-gcc41
-d, --distribution <distName>
  Which distribution for the selected package to install. <distName> can have three possible values:
 
  • source
    Installs just the source code for the distribution. Use this is if you want to build the software yourself.
 
  • user
    Installs all the binaries for the distribution. This is distribution for end users that just want to run the software.
 
  • developer
   

Installs everything, the source code and the binaries and is intended for use by those working to actively develop the software.

Note: This parameter is optional. If not present, it defaults to user.
-e, --extDir <dirName>
 

Location where external libraries are to be installed.

Defaults to $GLAST_EXT and then the local directory if $GLAST_EXT is not defined.
-i, --instDir <dirName>
 

Location where the packages are to be installed.

Defaults to $INST_DIR and then the local directory if $INST_DIR is not defined.
-x, --extOnly
  Only install the external libraries; don't install the tools.
-k, --pkgOnly
  Only install the packages; don't install the external libraries.
-r, --pretend
 

Doesn't actually install anything; just list the actions that would have been taken.

Notes:

  • This only affects the install command.
  • Giving this option causes everything to happen except for the actual downloading and installation of the files.
  • The installer will still perform all the check to make sure the selected installation package is available.
-f, --keepFiles
  Do not delete downloaded files once installation is complete. The default is to remove each installation file after the package has been installed. If this option is give, the files will remain on disk. They are downloaded to the /tmp directory.
Last updated by: Chuck Patterson 08/19/2010