installation.rst 8.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237
  1. .. include:: global.rst.inc
  2. .. _installation:
  3. Installation
  4. ============
  5. There are different ways to install |project_name|:
  6. - :ref:`distribution-package` - easy and fast if a package is
  7. available from your distribution.
  8. - :ref:`pyinstaller-binary` - easy and fast, we provide a ready-to-use binary file
  9. that comes bundled with all dependencies.
  10. - :ref:`source-install`, either:
  11. - :ref:`pip-installation` - installing a source package with pip needs
  12. more installation steps and requires all dependencies with
  13. development headers and a compiler.
  14. - :ref:`git-installation` - for developers and power users who want to
  15. have the latest code or use revision control (each release is
  16. tagged).
  17. .. _distribution-package:
  18. Distribution Package
  19. --------------------
  20. Some distributions might offer a ready-to-use ``borgbackup``
  21. package which can be installed with the package manager. As |project_name| is
  22. still a young project, such a package might be not available for your system
  23. yet.
  24. ============ ============================================= =======
  25. Distribution Source Command
  26. ============ ============================================= =======
  27. Arch Linux `[community]`_ ``pacman -S borg``
  28. Debian `stretch`_, `unstable/sid`_ ``apt install borgbackup``
  29. NixOS `.nix file`_ N/A
  30. OS X `Brew cask`_ ``brew cask install borgbackup``
  31. Ubuntu `Xenial 16.04`_, `Wily 15.10 (backport PPA)`_ ``apt install borgbackup``
  32. ============ ============================================= =======
  33. .. _[community]: https://www.archlinux.org/packages/?name=borg
  34. .. _stretch: https://packages.debian.org/stretch/borgbackup
  35. .. _unstable/sid: https://packages.debian.org/sid/borgbackup
  36. .. _Xenial 16.04: https://launchpad.net/ubuntu/xenial/+source/borgbackup
  37. .. _Wily 15.10 (backport PPA): https://launchpad.net/~neoatnhng/+archive/ubuntu/ppa
  38. .. _.nix file: https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/backup/borg/default.nix
  39. .. _Brew cask: http://caskroom.io/
  40. Please ask package maintainers to build a package or, if you can package /
  41. submit it yourself, please help us with that! See :issue:`105` on
  42. github to followup on packaging efforts.
  43. If a package is available, it might be interesting to check its version
  44. and compare that to our latest release and review the :doc:`changes`.
  45. .. _pyinstaller-binary:
  46. Standalone Binary
  47. -----------------
  48. |project_name| binaries (generated with `pyinstaller`_) are available
  49. on the releases_ page for the following platforms:
  50. * **Linux**: glibc >= 2.13 (ok for most supported Linux releases)
  51. * **Mac OS X**: 10.10 (unknown whether it works for older releases)
  52. * **FreeBSD**: 10.2 (unknown whether it works for older releases)
  53. To install such a binary, just drop it into a directory in your ``PATH``,
  54. make borg readable and executable for its users and then you can run ``borg``::
  55. sudo cp borg-linux64 /usr/local/bin/borg
  56. sudo chown root:root /usr/local/bin/borg
  57. sudo chmod 755 /usr/local/bin/borg
  58. Note that the binary uses /tmp to unpack |project_name| with all dependencies. It will fail if /tmp has not enough free space or is mounted with the ``noexec`` option. You can change the temporary directory by setting the ``TEMP`` environment variable before running |project_name|.
  59. If a new version is released, you will have to manually download it and replace
  60. the old version using the same steps as shown above.
  61. .. _pyinstaller: http://www.pyinstaller.org
  62. .. _releases: https://github.com/borgbackup/borg/releases
  63. .. _source-install:
  64. From Source
  65. -----------
  66. Dependencies
  67. ~~~~~~~~~~~~
  68. To install |project_name| from a source package (including pip), you have to install the
  69. following dependencies first:
  70. * `Python 3`_ >= 3.2.2. Even though Python 3 is not the default Python version on
  71. most systems, it is usually available as an optional install.
  72. * OpenSSL_ >= 1.0.0
  73. * libacl_ (that pulls in libattr_ also)
  74. * liblz4_
  75. * some Python dependencies, pip will automatically install them for you
  76. * optionally, the llfuse_ Python package is required if you wish to mount an
  77. archive as a FUSE filesystem. FUSE >= 2.8.0 is required for llfuse.
  78. In the following, the steps needed to install the dependencies are listed for a
  79. selection of platforms. If your distribution is not covered by these
  80. instructions, try to use your package manager to install the dependencies. On
  81. FreeBSD, you may need to get a recent enough OpenSSL version from FreeBSD
  82. ports.
  83. After you have installed the dependencies, you can proceed with steps outlined
  84. under :ref:`pip-installation`.
  85. Debian / Ubuntu
  86. +++++++++++++++
  87. Install the dependencies with development headers::
  88. sudo apt-get install python3 python3-dev python3-pip python-virtualenv \
  89. libssl-dev openssl \
  90. libacl1-dev libacl1 \
  91. liblz4-dev liblz4-1 \
  92. build-essential
  93. sudo apt-get install libfuse-dev fuse pkg-config # optional, for FUSE support
  94. In case you get complaints about permission denied on ``/etc/fuse.conf``: on
  95. Ubuntu this means your user is not in the ``fuse`` group. Add yourself to that
  96. group, log out and log in again.
  97. Fedora / Korora
  98. +++++++++++++++
  99. Install the dependencies with development headers::
  100. sudo dnf install python3 python3-devel python3-pip python3-virtualenv
  101. sudo dnf install openssl-devel openssl
  102. sudo dnf install libacl-devel libacl
  103. sudo dnf install lz4-devel
  104. sudo dnf install fuse-devel fuse pkgconfig # optional, for FUSE support
  105. Mac OS X
  106. ++++++++
  107. Assuming you have installed homebrew_, the following steps will install all the
  108. dependencies::
  109. brew install python3 lz4 openssl
  110. pip3 install virtualenv
  111. For FUSE support to mount the backup archives, you need at least version 3.0 of
  112. FUSE for OS X, which is available as a pre-release_.
  113. .. _pre-release: https://github.com/osxfuse/osxfuse/releases
  114. Cygwin
  115. ++++++
  116. .. note::
  117. Running under Cygwin is experimental and has only been tested with Cygwin
  118. (x86-64) v2.1.0.
  119. Use the Cygwin installer to install the dependencies::
  120. python3 python3-setuptools
  121. python3-cython # not needed for releases
  122. binutils gcc-core
  123. libopenssl openssl-devel
  124. liblz4_1 liblz4-devel # from cygwinports.org
  125. git make openssh
  126. You can then install ``pip`` and ``virtualenv``::
  127. easy_install-3.4 pip
  128. pip install virtualenv
  129. In case the creation of the virtual environment fails, try deleting this file::
  130. /usr/lib/python3.4/__pycache__/platform.cpython-34.pyc
  131. .. _pip-installation:
  132. Using pip
  133. ~~~~~~~~~
  134. Virtualenv_ can be used to build and install |project_name| without affecting
  135. the system Python or requiring root access. Using a virtual environment is
  136. optional, but recommended except for the most simple use cases.
  137. .. note::
  138. If you install into a virtual environment, you need to **activate** it
  139. first (``source borg-env/bin/activate``), before running ``borg``.
  140. Alternatively, symlink ``borg-env/bin/borg`` into some directory that is in
  141. your ``PATH`` so you can just run ``borg``.
  142. This will use ``pip`` to install the latest release from PyPi::
  143. virtualenv --python=python3 borg-env
  144. source borg-env/bin/activate
  145. # install Borg + Python dependencies into virtualenv
  146. pip install 'llfuse<0.41' # optional, for FUSE support
  147. # 0.41 and 0.41.1 have unicode issues at install time
  148. pip install borgbackup
  149. To upgrade |project_name| to a new version later, run the following after
  150. activating your virtual environment::
  151. pip install -U borgbackup
  152. .. _git-installation:
  153. Using git
  154. ~~~~~~~~~
  155. This uses latest, unreleased development code from git.
  156. While we try not to break master, there are no guarantees on anything. ::
  157. # get borg from github
  158. git clone https://github.com/borgbackup/borg.git
  159. virtualenv --python=python3 borg-env
  160. source borg-env/bin/activate # always before using!
  161. # install borg + dependencies into virtualenv
  162. pip install sphinx # optional, to build the docs
  163. pip install 'llfuse<0.41' # optional, for FUSE support
  164. # 0.41 and 0.41.1 have unicode issues at install time
  165. cd borg
  166. pip install -r requirements.d/development.txt
  167. pip install -e . # in-place editable mode
  168. # optional: run all the tests, on all supported Python versions
  169. # requires fakeroot, available through your package manager
  170. fakeroot -u tox
  171. .. note:: As a developer or power user, you always want to use a virtual environment.