This repository contains the scripts that are used to install some of the softwares listed in the ibnr_conf file.
The scripts in this folder install one software each. They may or may not install softwares from source. A script is the only solution when a simple add PPA, refresh and install flow does not do the job.
- An install script that installs software
foo-barshould be named asfoo-bar-install.shand a corresponding entry added to the ibnr-conf config file. - An install script should always exit with a value - 0 for no error and 1 for failure. This exit value is used by the install script to determine if the installation was successfull or not.
- An install script should never leave any background process and should always be blocking. This is because, once an install script exits, bnr's install script looks for an exit value to determine whether the operation was successful or not. Locking any resource or leaving background processes can interfere with other install scripts.
- An install script should carry out all of the steps in an installation without any user intervention. (Ex: accepting a license agreement, typing a password). This should be automated entirely by the install script as install scripts are executed inside a sub-shell and the user can't interact with the running script.
- All messages output by the install script to STDIN or STDERR is retained by bnr's install script for use in logging. Hence, additional error messages are encouraged and there needn't be any separate logging at the script level.
- It is strongly recommended to test the scripts on a fresh install of the Ubuntu version it is intended to work in.
- Stable versions are organized along the lines of Ubuntu's version number (Ex: 16.04 etc.) with corresponding dev branches. (Ex: 16.04-dev). Development and testing happens in the dev branches.
- The master branch is the main development branch which are merged into other version specific dev branches. When a dev branch is considered stable, it is merged into the stable branch.