lyp 0.0.5 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: b8b10bc684d3755cd63fde5175e4769e7ee8d1ae
-  data.tar.gz: dc4c7568047ba01915131cba0125e717f6c9f107
+  metadata.gz: eb8bf3168ca0cd5ed9769de74ce9511da0d657c8
+  data.tar.gz: d8275bb1f8533d3563b773671578c04efddc691f
 SHA512:
-  metadata.gz: 1f3845fec6418ec6221659d9f04a8e5d6919fd77fe714ee0d91a02f3664cc66ffc1c3e1189c1d8f903ad96bbeffce7e28e361c7ca098d780e76c2afbb80b80ca
-  data.tar.gz: 97ecbadebd13b96c51861c160c62b7e14f2546882d2cad65d9578c9488f2bed997abfb7678b8b43f8c04ee6bf5a4ddbb5f37b03b1c18a07d3947b1c8c8e72e91
+  metadata.gz: 991521014a20626dd4f22b8d894cd2430f5a4cc4c611e37d8600dee473b5a498ec8d5f8b3be339b622d17a471a3d058faab97ac216a489199feb016ee07b05cf
+  data.tar.gz: b6e1cd88cc53a4f6daf4776e12005095a03a5ca07db826ff95e0b5c16d040c60a8215d847dbed7be5d29c94a82fa5640ca7e399931139ebcdd302293fd9ac24c

data/LICENSE

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2015 Sharon Rosner
+Copyright (c) 2015-2016 Sharon Rosner
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/README.md

@@ -2,66 +2,197 @@
 
 # lyp - a package manager for lilypond
 
-lyp is a tool to install and manage packages for lilypond, and install versions of lilypond.
+Use lyp to install and manage packages for lilypond, and install and manage multiple versions of lilypond on your machine.
 
-lyp lets you install lilypond packages that act as code libraries and can be used to enhance your lilypond files with additional functionality. Packages can depend on other packages. Lyp resolves the direct and transitive package dependencies, and selects the correct version to use for each package.
+__Code reuse__: lyp lets you install packages that act as lilypond code libraries and can be used to enhance your lilypond files with additional functionality. Packages can depend on other packages. Lyp resolves both direct and transitive package dependencies, and automatically selects the correct version to use for each package.
 
-With lyp you can also install any version of lilypond on your machine with a single command, without having to visit the lilypond website, clicking a link and then copying files around. In addition, lyp lets you install multiple versions of lilypond and easily switch between them.
+__No hassle Lilypond installation__: With lyp you can also install any version of lilypond on your machine with a single command, without having to visit the lilypond website, clicking a link and then copying files around. In addition, lyp lets you switch between multiple versions of lilypond and always keep your machine up to date with the latest version.
 
-## What is a lilypond package?
+## Table of contents
+
+- [Installation](#installation)
+  - [How lyp works](#how-lyp-works)
+  - [Uninstalling](#uninstalling)
+- [Lilypond packages](#lilypond-packages)
+  - [What constitutes a package?](#what-constitutes-a-package)
+  - [Installing packages](#installing-packages)
+  - [Package references](#package-references)
+  - [Version specifiers](#version-specifiers)
+  - [Using packages](#using-packages)
+  - [Developing packages](#developing-packages)
+- [Installing and switching Lilypond versions](#installing-and-switching-lilypond-versions)
+- [Contributing](#contributing)
+
+## Installation
+
+**Note**: lyp is tested to work on Linux and Mac OSX. Installing and using it on Windows might be problematic.
+
+In order to install lyp, you need to have a relatively recent version of Ruby on your machine. You can then install lyp as a Ruby gem, and run the `install self` command:
+
+```bash
+gem install lyp
+lyp install self
+```
+
+(For those without Ruby on their machines, a self-contained version of lyp will be released in the near future.)
+
+The `lyp install self` command is needed in order to setup the `~/.lyp` working directory and add the lyp binaries directory to your `PATH` (see below), by adding a line of code to your shell profile file.
+
+### How lyp works
+
+Lyp sets up a working directory in `~/.lyp` where it keeps its binaries,  installed packages, and installed versions of lilypond. Lyp provides a wrapper script for lilypond, which does the following:
+
+- Select the correct version of lilypond to use (see below).
+- Scan the given lilypond file for any dependencies (specified using `\require`), and also recursively scan any include files for dependencies
+- Resolve the dependency tree and calculate the correct versions to use for each required package.
+- Create a wrapper lilypond file that loads the packages.
+- Invoke the selected version of lilypond.
+
+### Uninstalling
+
+In order to remove lyp from your system use the `uninstall self` command:
+
+```bash
+lyp uninstall self
+```
+
+This command will undo the changes made to your shell profile file, and remove any binaries from `~/.lyp/bin`.
+
+In order to completely remove all files in `~/.lyp` you can simply delete the directory:
+
+```bash
+rm -rf ~/.lyp
+```
+
+## Lilypond packages
 
 A package is a library of lilypond code, containing one or more lilypond files, that provide commonly-used functionality for users. A package can be a library of scheme code to extend lilypond, as in openlilylib; or a stylesheet which contains music fonts and additional lilypond code to change the look of the music: font, spacing, line widths, sizes, etc.
 
 The difference between merely copying and including a lilypond file in your music, and using a lilypond package is that you can easily share your music file with anyone and let them compile your music without having to download and copy additional code. lyp takes care of installing and resolving any dependencies in your lilypond files, so that you can compile your lilypond files anywhere without schlepping around a bunch of include files. Also, because packages are versioned, repeatable compilation using external code becomes trivial. 
 
-## How to add a package to your lilypond file?
+### What constitutes a package?
 
-Lilypond packages are simply git repositories. As such they can be identified by the repository's URL, or by the github repository path. To add a package dependency to your code, use the <code>\require</code> command:
+In lyp, a package should contain at least a single lilypond file named `package.ly` in its root directory. A package could contain additional lilypond files referenced in the main package file (using relative includes). A package could also depend on other packages by using the `\require` command (see below).
 
-```lilypond
-\require "lypco/lilyjazz" % repository is at: github.com/lypco/lilyjazz
-\require "github.com/lypco/poormans_henle"
+Lilypond packages are expected to be published as git repositories. The packages is then versioned using git tags. A package can be referenced either using its git URL, a short name (if it's registered in the [lyp package index](https://github.com/noteflakes/lyp-index)), or alternatively as a local path (which is meant for package development more than anything else).
+
+### Installing packages
+
+In order to install a package, use the `lyp install` command:
+
+```bash
+lyp install dummy # install latest version of package dummy
+lyp install github.com/ciconia/mypack@0.2.0 # install version 0.2.0
+lyp install mypack>=0.1.0 # install version 0.1.0 or higher
+lyp install mypack@dev:~/repo/mypack # install from local opath
 ```
 
-Versions can be specified either as specific versions, or as version specifiers which denote a range of versions:
+To uninstall the package, use the `lyp uninstall` command:
 
-```lilypond
-\require "lypco/lilyjazz@0.3.2"
+```bash
+lyp uninstall dummy@0.1.0 # uninstall version 0.1.0
+lyp uninstall -a dummy # uninstall all versions of dummy
+```
 
-% highest version higher than 0.3.2
-\require "lypco/lilyjazz@>=0.3.2"
+To list currently installed packages use `lyp list` command:
 
-% highest version higher than 0.4.5 but lower than 0.5.0
-\require "lypco/lilyjazz@~>0.4.5"
+```bash
+lyp list # list all installed packages
+lyp list font # list all installed packages matching the pattern 'font'
 ```
 
-Once the dependencies are specified, packages can be installed either using the <install> command:
-  
+To list packages available on the lyp package index use the `lyp search` command:
+
+```bash
+lyp search # list all packages in index
+lyp search stylesheet # list available packages matching pattern 'stylesheet'
+```
+
+### Package references
+
+A package is normally referenced by its git URL. Lyp lets you provide either fully- or partially qualified URLs. A package hosted on github can be also referenced by the user/repository pair. The following are all equivalent:
+
 ```bash
-lyp install "lypco/lilyjazz@0.3.2" % OR:
-lyp install "lypco/lilyjazz@>=0.3.2"
+lyp install https://github.com/noteflakes/lyp-package-template.git
+lyp install https://github.com/noteflakes/lyp-package-template
+lyp install github.com/noteflakes/lyp-package-template
+lyp install noteflakes/lyp-package-template
 ```
 
-... or the <code>resolve</code> command, which scans the user's file for dependencies and then installs them:
+In addition, lyp also provides an [index of publically available package](https://github.com/noteflakes/lyp-index), which maps a package name to its URL (see also below). Using the index, packages are referenced by their published name instead of by their git URL:
 
 ```bash
-lyp resolve maitre_sans_marteau.ly
+lyp install dummy
 ```
 
-## Installation
+To get a list of all available packages on the index, use the `lyp search` command.
 
-If you have Ruby on your machine, you can simply install the lyp gem, and run the install self command:
+### Version specifiers
+
+When installing packages defining package dependencies, it is advisable to specify the desired version to use. Using definitive versions lets you ensure that your third-party dependencies do not change unexpectedly and do not break your code.
+
+Versions can either be specified as specific version numbers, as version constraints or as descriptive names.
+
+Versions are specified using the ampersand character:
+
+```
+package@0.1.0
+package@stable
+```
+
+Version constraints specify a range of versions to use. Lyp currently supports two types of constraints:
+
+- Optimistic constraint: `package>=0.1.0`, which means any version equal to or higher than 0.1.0.
+- Pessimistic constraint: `package~>0.1.0`, which means any version equal or higher than 0.1.0, and lower than 0.2.0. This type of constraint is useful for packages which follow the semantic versioning standard.
+
+Version specifiers could be used when installing, listing and requiring packages, and also for specifying versions of lilypond (see below). For example:
 
 ```bash
-gem install lyp
-lyp install self
+lyp install "dummy~>0.2.0"
 ```
 
-## Installing packages with lyp
+(__Note__: that when using version constraints you should put the package specifier in quotes)
 
+### Using packages
 
+To include a package in your lilypond code, use ther `\require` command:
+
+```lilypond
+\require "dummy"
+\require "github.com/lulu/mypack>=0.4.0"
+```
+
+It is important to note that once you use `\require` in your code, you will have to compile it using the lilypond wrapper provided by lyp. It will not pass compilation using plain lilypond.
+
+### Developing packages
+
+To create a lilypond package:
+
+- Create a git repository.
+- Add a `package.ly` file, which is the main entry point for your package.
+- Optionally add additional lilypond files or package dependencies.
+- Test & debug your code (see below).
+- Publish your package (see below).
+
+To test your package code, you can install it from a local path. Suppose your package is at ~/repo/mypack:
+
+```bash
+lyp install mypack@dev:~/repo/mypack
+```
 
-## Installing and managing versions of lilypond
+This will create a `mypack@dev` package referencing your local files, which you can then reference from a test file in your package using the `\require` command:
+
+```lilypond
+\require "mypack@dev"
+```
+
+### Publishing packages
+
+In order for your package to be available to all users, you'll need to first push your code to a publically accessible git repository (for example on github). Users will then be able to install your package by using the git URL of the public repository.
+
+You can also add your package to the lyp [public package index](https://github.com/noteflakes/lyp-index), by cloning it, editing [index.yaml](https://github.com/noteflakes/lyp-index/blob/master/index.yaml), and creating a pull request.
+
+## Installing and switching Lilypond versions
 
 When installing lilypond, the specific version to download can be specified in different ways:
 
@@ -71,25 +202,48 @@ lyp install lilypond@stable % latest stable version
 lyp install lilypond@unstable % latest stable version
 lyp install lilypond@latest % latest version
 lyp install lilypond@2.18.1 % version 2.18.1
-lyp install lilypond@>=2.19.27 % highest version higher than 2.19.27
-lyp install lilypond@~>2.18.1 % highest 2.18 version higher than 2.18.1
+lyp install "lilypond>=2.19.27" % highest version higher than 2.19.27
+lyp install "lilypond~>2.18.1" % highest 2.18 version higher than 2.18.1
 ```
 
-To display all installed versions of lilypond, use the <code>list</code> command:
+To display all installed versions of lilypond, use the `list` command:
   
 ```bash
 lyp list lilypond
 ```
 
-To switch between versions use the <code>use</code>. The same version specifiers could be used as for the <code>install</code> command:
+This will also list any versions of lilypond found outside of the `~/.lyp` directory.
+
+You can also list available versions of lilypond by using the `search` command:
+
+```bash
+lyp search lilypond # display all available versions of lilypond
+lyp search "lilypond>=2.19" # display all available versions higher than 2.19
+lyp search "lilypond@stable" # display all available stable versions
+````
+
+To switch between versions use the `lyp use`. The same version specifiers could be used as for the `lyp install` command:
 
 ```bash
 lyp use lilypond@2.18.2 % or without the 'lilypond' identifier:
 lyp use stable % use latest stable version 
+lyp use unstable % use latest unstable version 
 ```
 
-To show all versions available for download, use the <code>search</code> command:
-  
+The setting of the current lilypond version to use will be maintained for the current shell session.
+
+In order to switch the default version of lilypond to use, add the `--default` switch:
+
+```bash
+lyp use --default 2.19.35
+```
+
+## Contributing
+
+Lyp is written in Ruby, and its code is [available on github](https://github.com/noteflakes/lyp). To hack on it, siply clone the repository. To run the specs:
+
 ```bash
-lyp search lilypond
-```
+rspec
+```
+
+Please feel free to submit issues and pull requests.

data/bin/get.sh

@@ -0,0 +1,886 @@
+#!/usr/bin/env bash
+
+shopt -s extglob
+set -o errtrace
+set -o errexit
+
+rvm_install_initialize()
+{
+  DEFAULT_SOURCES=(github.com/rvm/rvm bitbucket.org/mpapis/rvm)
+
+  BASH_MIN_VERSION="3.2.25"
+  if
+    [[ -n "${BASH_VERSION:-}" &&
+      "$(\printf "%b" "${BASH_VERSION:-}\n${BASH_MIN_VERSION}\n" | LC_ALL=C \sort -t"." -k1,1n -k2,2n -k3,3n | \head -n1)" != "${BASH_MIN_VERSION}"
+    ]]
+  then
+    echo "BASH ${BASH_MIN_VERSION} required (you have $BASH_VERSION)"
+    exit 1
+  fi
+
+  export HOME PS4
+  export rvm_trace_flag rvm_debug_flag rvm_user_install_flag rvm_ignore_rvmrc rvm_prefix rvm_path
+
+  PS4="+ \${BASH_SOURCE##\${rvm_path:-}} : \${FUNCNAME[0]:+\${FUNCNAME[0]}()}  \${LINENO} > "
+}
+
+log()  { printf "%b\n" "$*"; }
+debug(){ [[ ${rvm_debug_flag:-0} -eq 0 ]] || printf "%b\n" "Running($#): $*"; }
+fail() { log "\nERROR: $*\n" ; exit 1 ; }
+
+rvm_install_commands_setup()
+{
+  \which which >/dev/null 2>&1 || fail "Could not find 'which' command, make sure it's available first before continuing installation."
+  if
+    [[ -z "${rvm_tar_command:-}" ]] && builtin command -v gtar >/dev/null
+  then
+    rvm_tar_command=gtar
+  elif
+    ${rvm_tar_command:-tar} --help 2>&1 | GREP_OPTIONS="" \grep -- --strip-components >/dev/null
+  then
+    rvm_tar_command="${rvm_tar_command:-tar}"
+  else
+    case "$(uname)" in
+      (OpenBSD)
+        log "Trying to install GNU version of tar, might require sudo password"
+        if (( UID ))
+        then sudo pkg_add -z gtar-1
+        else pkg_add -z gtar-1
+        fi
+        rvm_tar_command=gtar
+        ;;
+      (Darwin|FreeBSD|DragonFly) # it's not possible to autodetect on OSX, the help/man does not mention all flags
+        rvm_tar_command=tar
+        ;;
+      (SunOS)
+        case "$(uname -r)" in
+          (5.10)
+            log "Trying to install GNU version of tar, might require sudo password"
+            if (( UID ))
+            then
+              if \which sudo >/dev/null 2>&1
+              then sudo_10=sudo
+              elif \which /opt/csw/bin/sudo >/dev/null 2>&1
+              then sudo_10=/opt/csw/bin/sudo
+              else fail "sudo is required but not found. You may install sudo from OpenCSW repository (http://opencsw.org/about)"
+              fi
+              pkginfo -q CSWpkgutil || $sudo_10 pkgadd -a $rvm_path/config/solaris/noask -d http://get.opencsw.org/now CSWpkgutil
+              sudo /opt/csw/bin/pkgutil -iy CSWgtar -t http://mirror.opencsw.org/opencsw/unstable
+            else
+              pkginfo -q CSWpkgutil || pkgadd -a $rvm_path/config/solaris/noask -d http://get.opencsw.org/now CSWpkgutil
+              /opt/csw/bin/pkgutil -iy CSWgtar -t http://mirror.opencsw.org/opencsw/unstable
+            fi
+            rvm_tar_command=/opt/csw/bin/gtar
+            ;;
+          (*)
+            rvm_tar_command=tar
+            ;;
+        esac
+    esac
+    builtin command -v ${rvm_tar_command:-gtar} >/dev/null ||
+    fail "Could not find GNU compatible version of 'tar' command, make sure it's available first before continuing installation."
+  fi
+  if
+    [[ " ${rvm_tar_options:-} " != *" --no-same-owner "*  ]] &&
+    $rvm_tar_command --help 2>&1 | GREP_OPTIONS="" \grep -- --no-same-owner >/dev/null
+  then
+    rvm_tar_options="${rvm_tar_options:-}${rvm_tar_options:+ }--no-same-owner"
+  fi
+}
+
+usage()
+{
+  printf "%b" "
+
+Usage
+
+  rvm-installer [options] [action]
+
+Options
+
+  [[--]version] <version>
+
+    The version or tag to install. Valid values are:
+
+      latest         - The latest tagged version.
+      latest-minor   - The latest minor version of the current major version.
+      latest-<x>     - The latest minor version of version x.
+      latest-<x>.<y> - The latest patch version of version x.y.
+      <x>.<y>.<z>    - Major version x, minor version y and patch z.
+
+  [--]branch <branch>
+
+    The name of the branch from which RVM is installed. This option can be used
+    with the following formats for <branch>:
+
+      <account>/
+
+        If account is wayneeseguin or mpapis, installs from one of the following:
+
+          https://github.com/rvm/rvm/archive/master.tar.gz
+          https://bitbucket.org/mpapis/rvm/get/master.tar.gz
+
+       Otherwise, installs from:
+
+         https://github.com/<account>/rvm/archive/master.tar.gz
+
+      <account>/<branch>
+
+        If account is wayneeseguin or mpapis, installs from one of the following:
+
+          https://github.com/rvm/rvm/archive/<branch>.tar.gz
+          https://bitbucket.org/mpapis/rvm/get/<branch>.tar.gz
+
+        Otherwise, installs from:
+
+          https://github.com/<account>/rvm/archive/<branch>.tar.gz
+
+      [/]<branch>
+
+        Installs the branch from one of the following:
+
+          https://github.com/rvm/rvm/archive/<branch>.tar.gz
+          https://bitbucket.org/mpapis/rvm/get/<branch>.tar.gz
+
+      [--]source <source>
+
+        Defines the repository from which RVM is retrieved and installed in the format:
+
+          <domain>/<account>/<repo>
+
+        Where:
+
+          <domain>  - Is bitbucket.org, github.com or a github enterprise site serving
+                      an RVM repository.
+          <account> - Is the user account in which the RVM repository resides.
+          <repo>    - Is the name of the RVM repository.
+
+        Note that when using the [--]source option, one should only use the [/]branch format
+        with the [--]branch option. Failure to do so will result in undefined behavior.
+
+      --trace
+
+        Provides debug logging for the installation script.
+Actions
+
+  master - Installs RVM from the master branch at rvm/rvm on github or mpapis/rvm
+           on bitbucket.org.
+  stable - Installs RVM from the stable branch a rvm/rvm on github or mpapis/rvm
+           on bitbucket.org.
+  help   - Displays this output.
+
+"
+}
+
+## duplication marker 32fosjfjsznkjneuera48jae
+__rvm_curl_output_control()
+{
+  if
+    (( ${rvm_quiet_curl_flag:-0} == 1 ))
+  then
+    __flags+=( "--silent" "--show-error" )
+  elif
+    [[ " $*" == *" -s"* || " $*" == *" --silent"* ]]
+  then
+    # make sure --show-error is used with --silent
+    [[ " $*" == *" -S"* || " $*" == *" -sS"* || " $*" == *" --show-error"* ]] ||
+    {
+      __flags+=( "--show-error" )
+    }
+  fi
+}
+
+## duplication marker 32fosjfjsznkjneuera48jae
+# -S is automatically added to -s
+__rvm_curl()
+(
+  __rvm_which curl >/dev/null ||
+  {
+    rvm_error "RVM requires 'curl'. Install 'curl' first and try again."
+    return 200
+  }
+
+  typeset -a __flags
+  __flags=( --fail --location --max-redirs 10 )
+
+  [[ "$*" == *"--max-time"* ]] ||
+  [[ "$*" == *"--connect-timeout"* ]] ||
+    __flags+=( --connect-timeout 30 --retry-delay 2 --retry 3 )
+
+  if [[ -n "${rvm_proxy:-}" ]]
+  then __flags+=( --proxy "${rvm_proxy:-}" )
+  fi
+
+  __rvm_curl_output_control
+
+  unset curl
+  __rvm_debug_command \curl "${__flags[@]}" "$@" || return $?
+)
+
+rvm_error()  { printf "ERROR: %b\n" "$*"; }
+__rvm_which(){   which "$@" || return $?; true; }
+__rvm_debug_command()
+{
+  debug "Running($#): $*"
+  "$@" || return $?
+  true
+}
+rvm_is_a_shell_function()
+{
+  [[ -t 0 && -t 1 ]] || return $?
+  return ${rvm_is_not_a_shell_function:-0}
+}
+
+# Searches the tags for the highest available version matching a given pattern.
+# fetch_version (github.com/rvm/rvm bitbucket.org/mpapis/rvm) 1.10. -> 1.10.3
+# fetch_version (github.com/rvm/rvm bitbucket.org/mpapis/rvm) 1.10. -> 1.10.3
+# fetch_version (github.com/rvm/rvm bitbucket.org/mpapis/rvm) 1.    -> 1.11.0
+# fetch_version (github.com/rvm/rvm bitbucket.org/mpapis/rvm) ""    -> 2.0.1
+fetch_version()
+{
+  typeset _account _domain _pattern _repo _sources _values _version
+  _sources=(${!1})
+  _pattern=$2
+  for _source in "${_sources[@]}"
+  do
+    IFS='/' read -r _domain _account _repo <<< "${_source}"
+    _version="$(
+      fetch_versions ${_domain} ${_account} ${_repo} |
+      GREP_OPTIONS="" \grep "^${_pattern:-}" | tail -n 1
+    )"
+    if
+      [[ -n ${_version} ]]
+    then
+      echo "${_version}"
+      return 0
+    fi
+  done
+}
+
+# Returns a sorted list of all version tags from a repository
+fetch_versions()
+{
+  typeset _account _domain _repo _url
+  _domain=$1
+  _account=$2
+  _repo=$3
+  case ${_domain} in
+    (bitbucket.org)
+      _url=https://${_domain}/api/1.0/repositories/${_account}/${_repo}/branches-tags
+      ;;
+    (github.com)
+      _url=https://api.${_domain}/repos/${_account}/${_repo}/tags
+      ;;
+
+    (*)
+      _url=https://${_domain}/api/v3/repos/${_account}/${_repo}/tags
+      ;;
+  esac
+  __rvm_curl -s ${_url} |
+    \awk -v RS=',' -v FS='"' '$2=="name"{print $4}' |
+    sort -t. -k 1,1n -k 2,2n -k 3,3n -k 4,4n -k 5,5n
+}
+
+install_release()
+{
+  typeset _source _sources _url _version _verify_pgp
+  _sources=(${!1})
+  _version=$2
+  debug "Downloading RVM version ${_version}"
+  for _source in "${_sources[@]}"
+  do
+    case ${_source} in
+      (bitbucket.org*)
+        _url="https://${_source}/get/${_version}.tar.gz"
+        _verify_pgp="https://${_source}/downloads/${_version}.tar.gz.asc"
+        ;;
+      (*)
+        _url="https://${_source}/archive/${_version}.tar.gz"
+        _verify_pgp="https://${_source}/releases/download/${_version}/${_version}.tar.gz.asc"
+        ;;
+    esac
+    get_and_unpack "${_url}" "rvm-${_version}.tgz" "$_verify_pgp" && return
+  done
+  return $?
+}
+
+install_head()
+{
+  typeset _branch _source _sources _url
+  _sources=(${!1})
+  _branch=$2
+  debug "Selected RVM branch ${_branch}"
+  for _source in "${_sources[@]}"
+  do
+    case ${_source} in
+      (bitbucket.org*)
+        _url=https://${_source}/get/${_branch}.tar.gz
+        ;;
+      (*)
+        _url=https://${_source}/archive/${_branch}.tar.gz
+        ;;
+    esac
+    get_and_unpack "${_url}" "rvm-${_branch//\//_}.tgz" && return
+  done
+  return $?
+}
+
+# duplication marker dfkjdjngdfjngjcszncv
+# Drop in cd which _doesn't_ respect cdpath
+__rvm_cd()
+{
+  typeset old_cdpath ret
+  ret=0
+  old_cdpath="${CDPATH}"
+  CDPATH="."
+  chpwd_functions="" builtin cd "$@" || ret=$?
+  CDPATH="${old_cdpath}"
+  return $ret
+}
+
+get_package()
+{
+  typeset _url _file
+  _url="$1"
+  _file="$2"
+  log "Downloading ${_url}"
+  __rvm_curl -sS ${_url} -o ${rvm_archives_path}/${_file} ||
+  {
+    _return=$?
+    case $_return in
+      # duplication marker lfdgzkngdkjvnfjknkjvcnbjkncvjxbn
+      (60)
+        log "
+Could not download '${_url}', you can read more about it here:
+https://rvm.io/support/fixing-broken-ssl-certificates/
+To continue in insecure mode run 'echo insecure >> ~/.curlrc'.
+"
+        ;;
+      # duplication marker lfdgzkngdkjvnfjknkjvcnbjkncvjxbn
+      (77)
+        log "
+It looks like you have old certificates, you can read more about it here:
+https://rvm.io/support/fixing-broken-ssl-certificates/
+"
+        ;;
+      # duplication marker lfdgzkngdkjvnfjknkjvcnbjkncvjxbn
+      (141)
+        log "
+Curl returned 141 - it is result of a segfault which means it's Curls fault.
+Try again and if it crashes more than a couple of times you either need to
+reinstall Curl or consult with your distribution manual and contact support.
+"
+        ;;
+      (*)
+        log "
+Could not download '${_url}'.
+  curl returned status '$_return'.
+"
+        ;;
+    esac
+    return $_return
+  }
+}
+
+# duplication marker flnglfdjkngjndkfjhsbdjgfghdsgfklgg
+rvm_install_gpg_setup()
+{
+  export rvm_gpg_command
+  {
+    rvm_gpg_command="$( \which gpg2 2>/dev/null )" &&
+    [[ ${rvm_gpg_command} != "/cygdrive/"* ]]
+  } ||
+    rvm_gpg_command="$( \which gpg 2>/dev/null )" ||
+    rvm_gpg_command=""
+  debug "Detected GPG program: '$rvm_gpg_command'"
+  [[ -n "$rvm_gpg_command" ]] || return $?
+}
+
+# duplication marker rdjgndfnghdfnhgfdhbghdbfhgbfdhbn
+verify_package_pgp()
+{
+  if
+    "${rvm_gpg_command}" --verify "$2" "$1"
+  then
+    log "GPG verified '$1'"
+  else
+    typeset _ret=$?
+    log "\
+Warning, RVM 1.26.0 introduces signed releases and \
+automated check of signatures when GPG software found.
+Assuming you trust Michal Papis import the mpapis public \
+key (downloading the signatures).
+
+GPG signature verification failed for '$1' - '$3'!
+try downloading the signatures:
+
+    ${SUDO_USER:+sudo }${rvm_gpg_command##*/} --keyserver hkp://keys.gnupg.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3
+
+or if it fails:
+
+    command curl -sSL https://rvm.io/mpapis.asc | ${SUDO_USER:+sudo }${rvm_gpg_command##*/} --import -
+
+the key can be compared with:
+
+    https://rvm.io/mpapis.asc
+    https://keybase.io/mpapis
+"
+    exit $_ret
+  fi
+}
+
+verify_pgp()
+{
+  [[ -n "${1:-}" ]] ||
+  {
+    debug "No PGP url given, skipping."
+    return 0
+  }
+
+  get_package "$1" "$2.asc" ||
+  {
+    debug "PGP url given but does not exist: '$1'"
+    return 0
+  }
+
+  rvm_install_gpg_setup ||
+  {
+    log "Found PGP signature at: '$1',
+but no GPG software exists to validate it, skipping."
+    return 0
+  }
+
+  verify_package_pgp "${rvm_archives_path}/$2" "${rvm_archives_path}/$2.asc" "$1"
+}
+
+get_and_unpack()
+{
+  typeset _url _file _patern _return _verify_pgp
+  _url="$1"
+  _file="$2"
+  _verify_pgp="$3"
+
+  get_package "$_url" "$_file" || return $?
+  verify_pgp "$_verify_pgp" "$_file" || return $?
+
+  [[ -d "${rvm_src_path}/rvm" ]] || \mkdir -p "${rvm_src_path}/rvm"
+  __rvm_cd "${rvm_src_path}/rvm" ||
+  {
+    _return=$?
+    log "Could not change directory '${rvm_src_path}/rvm'."
+    return $_return
+  }
+
+  rm -rf ${rvm_src_path}/rvm/*
+  __rvm_debug_command $rvm_tar_command xzf ${rvm_archives_path}/${_file} ${rvm_tar_options:-} --strip-components 1 ||
+  {
+    _return=$?
+    log "Could not extract RVM sources."
+    return $_return
+  }
+}
+
+rvm_install_default_settings()
+{
+  # Tracing, if asked for.
+  if
+    [[ "$*" == *--trace* ]] || (( ${rvm_trace_flag:-0} > 0 ))
+  then
+    set -o xtrace
+    rvm_trace_flag=1
+  fi
+
+  # Variable initialization, remove trailing slashes if they exist on HOME
+  true \
+    ${rvm_trace_flag:=0} ${rvm_debug_flag:=0}\
+    ${rvm_ignore_rvmrc:=0} HOME="${HOME%%+(\/)}"
+
+  if
+    (( rvm_ignore_rvmrc == 0 ))
+  then
+    for rvmrc in /etc/rvmrc "$HOME/.rvmrc"
+    do
+      if
+        [[ -s "$rvmrc" ]]
+      then
+        if
+          GREP_OPTIONS="" \grep '^\s*rvm .*$' "$rvmrc" >/dev/null 2>&1
+        then
+          printf "%b" "
+  Error: $rvmrc is for rvm settings only.
+  rvm CLI may NOT be called from within $rvmrc.
+  Skipping the loading of $rvmrc
+  "
+          exit 1
+        else
+          source "$rvmrc"
+        fi
+      fi
+    done
+  fi
+
+  if
+    [[ -z "${rvm_path:-}" ]]
+  then
+    if
+      (( UID == 0 ))
+    then
+      rvm_user_install_flag=0
+      rvm_prefix="/usr/local"
+      rvm_path="${rvm_prefix}/rvm"
+    else
+      rvm_user_install_flag=1
+      rvm_prefix="$HOME"
+      rvm_path="${rvm_prefix}/.rvm"
+    fi
+  fi
+  if [[ -z "${rvm_prefix}" ]]
+  then rvm_prefix=$( dirname $rvm_path )
+  fi
+
+  # duplication marker kkdfkgnjfndgjkndfjkgnkfjdgn
+  [[ -n "${rvm_user_install_flag:-}" ]] ||
+  case "$rvm_path" in
+    (/usr/local/rvm)         rvm_user_install_flag=0 ;;
+    ($HOME/*|/${USER// /_}*) rvm_user_install_flag=1 ;;
+    (*)                      rvm_user_install_flag=0 ;;
+  esac
+}
+
+rvm_install_parse_params()
+{
+  install_rubies=()
+  install_gems=()
+  flags=( ./scripts/install )
+  forwarded_flags=()
+  while
+    (( $# > 0 ))
+  do
+    token="$1"
+    shift
+    case "$token" in
+
+      (--trace)
+        set -o xtrace
+        rvm_trace_flag=1
+        flags=( -x "${flags[@]}" "$token" )
+        forwarded_flags+=( "$token" )
+        ;;
+
+      (--debug|--quiet-curl)
+        flags+=( "$token" )
+        forwarded_flags+=( "$token" )
+        token=${token#--}
+        token=${token//-/_}
+        export "rvm_${token}_flag"=1
+        printf "%b" "Turning on ${token/_/ } mode.\n"
+        ;;
+
+      (--path)
+        if [[ -n "${1:-}" ]]
+        then
+          rvm_path="$1"
+          shift
+        else
+          fail "--path must be followed by a path."
+        fi
+        ;;
+
+      (--branch|branch) # Install RVM from a given branch
+        if [[ -n "${1:-}" ]]
+        then
+          case "$1" in
+            (/*)
+              branch=${1#/}
+              ;;
+            (*/)
+              branch=master
+              if [[ "${1%/}" -ne wayneeseguin ]] && [[ "${1%/}" -ne mpapis ]]
+              then sources=(github.com/${1%/}/rvm)
+              fi
+              ;;
+            (*/*)
+              branch=${1#*/}
+              if [[ "${1%%/*}" -ne wayneeseguin ]] && [[ "${1%%/*}" -ne mpapis ]]
+              then sources=(github.com/${1%%/*}/rvm)
+              fi
+              ;;
+            (*)
+              branch="$1"
+              ;;
+          esac
+          shift
+        else
+          fail "--branch must be followed by a branchname."
+        fi
+        ;;
+
+      (--source|source)
+        if [[ -n "${1:-}" ]]
+        then
+          if [[ "$1" = */*/* ]]
+          then
+            sources=($1)
+            shift
+          else
+            fail "--source must be in the format <domain>/<account>/<repo>."
+          fi
+        else
+          fail "--source must be followed by a source."
+        fi
+        ;;
+
+      (--user-install|--ignore-dotfiles)
+        token=${token#--}
+        token=${token//-/_}
+        export "rvm_${token}_flag"=1
+        printf "%b" "Turning on ${token/_/ } mode.\n"
+        ;;
+
+      (--auto-dotfiles)
+        flags+=( "$token" )
+        export "rvm_auto_dotfiles_flag"=1
+        printf "%b" "Turning on auto dotfiles mode.\n"
+        ;;
+
+      (--auto)
+        export "rvm_auto_dotfiles_flag"=1
+        printf "%b" "Warning, --auto is deprecated in favor of --auto-dotfiles.\n"
+        ;;
+
+      (--verify-downloads)
+        if [[ -n "${1:-}" ]]
+        then
+          export rvm_verify_downloads_flag="$1"
+          forwarded_flags+=( "$token" "$1" )
+          shift
+        else
+          fail "--verify-downloads must be followed by level(0|1|2)."
+        fi
+        ;;
+
+      (--autolibs=*)
+        flags+=( "$token" )
+        export rvm_autolibs_flag="${token#--autolibs=}"
+        forwarded_flags+=( "$token" )
+        ;;
+
+      (--without-gems=*|--with-gems=*|--with-default-gems=*)
+        flags+=( "$token" )
+        value="${token#*=}"
+        token="${token%%=*}"
+        token="${token#--}"
+        token="${token//-/_}"
+        export "rvm_${token}"="${value}"
+        printf "%b" "Installing RVM ${token/_/ }: ${value}.\n"
+        ;;
+
+      (--version|version)
+        version="$1"
+        shift
+        ;;
+
+      (head|master)
+        version="head"
+        branch="master"
+        ;;
+
+      (stable)
+        version="latest"
+        ;;
+
+      (latest|latest-*|+([[:digit:]]).+([[:digit:]]).+([[:digit:]]))
+        version="$token"
+        ;;
+
+      (--ruby)
+        install_rubies+=( ruby )
+        ;;
+
+      (--ruby=*)
+        token=${token#--ruby=}
+        install_rubies+=( ${token//,/ } )
+        ;;
+
+      (--rails)
+        install_gems+=( rails )
+        ;;
+
+      (--gems=*)
+        token=${token#--gems=}
+        install_gems+=( ${token//,/ } )
+        ;;
+
+      (--add-to-rvm-group)
+        export rvm_add_users_to_rvm_group="$1"
+        shift
+        ;;
+
+      (help|usage)
+        usage
+        exit 0
+        ;;
+
+      (*)
+        usage
+        exit 1
+        ;;
+
+    esac
+  done
+
+  if (( ${#install_gems[@]} > 0 && ${#install_rubies[@]} == 0 ))
+  then install_rubies=( ruby )
+  fi
+
+  true "${version:=head}"
+  true "${branch:=master}"
+
+  if [[ -z "${sources[@]}" ]]
+  then sources=("${DEFAULT_SOURCES[@]}")
+  fi
+
+  rvm_src_path="$rvm_path/src"
+  rvm_archives_path="$rvm_path/archives"
+  rvm_releases_url="https://rvm.io/releases"
+}
+
+rvm_install_validate_rvm_path()
+{
+  case "$rvm_path" in
+    (*[[:space:]]*)
+      printf "%b" "
+It looks you are one of the happy *space* users(in home dir name),
+RVM is not yet fully ready for it, use this trick to fix it:
+
+    sudo mkdir -p /${USER// /_}.rvm
+    sudo chown -R \"$USER:\" /${USER// /_}.rvm
+    echo \"export rvm_path=/${USER// /_}.rvm\" >> \"$HOME/.rvmrc\"
+
+and start installing again.
+
+"
+      exit 2
+    ;;
+    (/usr/share/ruby-rvm)
+      printf "%b" "
+It looks you are one of the happy Ubuntu users,
+RVM packaged by Ubuntu is old and broken,
+follow this link for details how to fix:
+
+  http://stackoverflow.com/a/9056395/497756
+
+"
+      [[ "${rvm_uses_broken_ubuntu_path:-no}" == "yes" ]] || exit 3
+    ;;
+  esac
+
+  if [[ "$rvm_path" != "/"* ]]
+  then fail "The rvm install path must be fully qualified. Tried $rvm_path"
+  fi
+}
+
+rvm_install_select_and_get_version()
+{
+  typeset _version_release
+
+  for dir in "$rvm_src_path" "$rvm_archives_path"
+  do
+    [[ -d "$dir" ]] || mkdir -p "$dir"
+  done
+
+  _version_release="${version}"
+  case "${version}" in
+    (head)
+      _version_release="${branch}"
+      install_head sources[@] ${branch:-master} || exit $?
+      ;;
+
+    (latest)
+      install_release sources[@] $(fetch_version sources[@]) || exit $?
+      ;;
+
+    (latest-minor)
+      version="$(\cat "$rvm_path/VERSION")"
+      install_release sources[@] $(fetch_version sources[@] ${version%.*}) || exit $?
+      ;;
+
+    (latest-*)
+      install_release sources[@] $(fetch_version sources[@] ${version#latest-}) || exit $?
+      ;;
+
+    (+([[:digit:]]).+([[:digit:]]).+([[:digit:]])) # x.y.z
+      install_release sources[@] ${version} || exit $?
+      ;;
+
+    (*)
+      fail "Something went wrong, unrecognized version '$version'"
+      ;;
+  esac
+  echo "${_version_release}" > "$rvm_path/RELEASE"
+}
+
+rvm_install_main()
+{
+  [[ -f ./scripts/install ]] ||
+  {
+    log "'./scripts/install' can not be found for installation, something went wrong, it usally means your 'tar' is broken, please report it here: https://github.com/rvm/rvm/issues"
+    return 127
+  }
+
+  # required flag - path to install
+  flags+=( --path "$rvm_path" )
+  \command bash "${flags[@]}"
+}
+
+rvm_install_ruby_and_gems()
+(
+  if
+    (( ${#install_rubies[@]} > 0 ))
+  then
+    source ${rvm_scripts_path:-${rvm_path}/scripts}/rvm
+    source ${rvm_scripts_path:-${rvm_path}/scripts}/version
+    __rvm_version
+
+    for _ruby in ${install_rubies[@]}
+    do command rvm "${forwarded_flags[@]}" install ${_ruby} -j 2
+    done
+    # set the first one as default, skip rest
+    for _ruby in ${install_rubies[@]}
+    do
+      rvm "${forwarded_flags[@]}" alias create default ${_ruby}
+      break
+    done
+
+    for _gem in ${install_gems[@]}
+    do rvm "${forwarded_flags[@]}" all do gem install ${_gem}
+    done
+
+    printf "%b" "
+  * To start using RVM you need to run \`source $rvm_path/scripts/rvm\`
+    in all your open shell windows, in rare cases you need to reopen all shell windows.
+"
+
+    if
+      [[ "${install_gems[*]}" == *"rails"* ]]
+    then
+      printf "%b" "
+  * To start using rails you need to run \`rails new <project_dir>\`.
+"
+    fi
+  fi
+)
+
+rvm_install()
+{
+  rvm_install_initialize
+  rvm_install_commands_setup
+  rvm_install_default_settings
+  rvm_install_parse_params "$@"
+  rvm_install_validate_rvm_path
+  rvm_install_select_and_get_version
+  rvm_install_main
+  rvm_install_ruby_and_gems
+}
+
+rvm_install "$@"