Giter Site home page Giter Site logo

install_scripts's Introduction

Description

This repository contains the scripts that are used to install some of the softwares listed in the ibnr_conf file.

Getting Started and Contributing

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.

Conventions and guidelines for creating an install script####

  • An install script that installs software foo-bar should be named as foo-bar-install.sh and 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.

Versioning and Contributing

  • 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.

LICENSE

GNU GPLv3

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.