This sub-directory contains:
- The Install Script(Install)
- The Package Config File(bowtie2_package.cfg)
- The Package Dependencies File(bowtie2_dependencies.cfg)
After installing the package_downloads repos
See: https://github.com/mdibl/package_downloads/wiki/How-To-Install-This-Repos
cd to package_downloads/ install root directory and run
Example 1: ./trigger_tool_install.sh bowtie2
The above command tells the trigger script to install the current version of bowtie2
Example 2: ./trigger_tool_install.sh bowtie2 v2.3.3.1
The above command tells the trigger script to install version v2.3.3.2
This script is called by the main install script (install_package.sh) to build and install a new version of the package
- sources the main config file to set global path
- sources the dependencies config file
- runs the build and copy the executables to /opt/software/bin
The following environment variables are expected to be set by the caller:
- GLOBAL_CONFIG (Path to the main Configuration file
${PACKAGE_DOWNLOADS_BASE}/Configuration )
- PACKAGE_BASE (Path to the new release install directory ${EXTERNAL_SOFTWARE_BASE}/${SHORT_NAME}/${RELEASE_DIR})
- PACKAGE_DEPENDENCIES_FILE (The dependencies file for this tool PACKAGE_DOWNLOADS_BASE/SHORT_NAME/
The config file sets environment variables specific to this tool. Some key variables include:
- GIT_ORG
- SHORT_NAME (same as the name of the tool local directory)
- GIT_REPOS
- REMOTE_SITE
- REMOTE_DIR
- REPOS_TAG_PATTERN
- REMOTE_VERSION_FILE
- RELEASE_DIR
- EXPORT_GIT
- CLONE_GIT
Each tool's dependency file contains the pre-install and post-install sets of dependencies. Bowtie2 only uses few of these variables.
- BIN_DEPENDENCIES
- LIB_DEPENDENCIES
- FILE_CHECK
- DIR_CHECK
- BIN_FILES
- INCLUDE_DIR
- LIB64_DIR
- LIB_DIR