installation.rst 7.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216
  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 / for your operating system.
  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 Linux and BSD 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. * On **Arch Linux**, there is a package available in the AUR_.
  25. .. _AUR: https://aur.archlinux.org/packages/borgbackup/
  26. Please ask package maintainers to build a package or, if you can package /
  27. submit it yourself, please help us with that! See :issue:`105` on
  28. github to followup on packaging efforts.
  29. If a package is available, it might be interesting to check its version
  30. and compare that to our latest release and review the :doc:`changes`.
  31. .. _pyinstaller-binary:
  32. Standalone Binary
  33. -----------------
  34. |project_name| binaries (generated with `pyinstaller`_) are available
  35. on the releases_ page for the following platforms:
  36. * **Linux**: glibc >= 2.13 (ok for most supported Linux releases)
  37. * **Mac OS X**: 10.10 (unknown whether it works for older releases)
  38. * **FreeBSD**: 10.2 (unknown whether it works for older releases)
  39. These binaries work without requiring specific installation steps. Just drop
  40. them into a directory in your ``PATH`` and then you can run ``borg``. If a new
  41. version is released, you will have to manually download it and replace the old
  42. version.
  43. .. _pyinstaller: http://www.pyinstaller.org
  44. .. _releases: https://github.com/borgbackup/borg/releases
  45. .. _source-install:
  46. From Source
  47. -----------
  48. Dependencies
  49. ~~~~~~~~~~~~
  50. To install |project_name| from a source package (including pip), you have to install the
  51. following dependencies first:
  52. * `Python 3`_ >= 3.2.2. Even though Python 3 is not the default Python version on
  53. most systems, it is usually available as an optional install.
  54. * OpenSSL_ >= 1.0.0
  55. * libacl_ (that pulls in libattr_ also)
  56. * liblz4_
  57. * some Python dependencies, pip will automatically install them for you
  58. * optionally, the llfuse_ Python package is required if you wish to mount an
  59. archive as a FUSE filesystem. FUSE >= 2.8.0 is required for llfuse.
  60. In the following, the steps needed to install the dependencies are listed for a
  61. selection of platforms. If your distribution is not covered by these
  62. instructions, try to use your package manager to install the dependencies. On
  63. FreeBSD, you may need to get a recent enough OpenSSL version from FreeBSD
  64. ports.
  65. After you have installed the dependencies, you can proceed with steps outlined
  66. under :ref:`pip-installation`.
  67. Debian / Ubuntu
  68. +++++++++++++++
  69. Install the dependencies with development headers::
  70. sudo apt-get install python3 python3-dev python3-pip python-virtualenv
  71. sudo apt-get install libssl-dev openssl
  72. sudo apt-get install libacl1-dev libacl1
  73. sudo apt-get install liblz4-dev liblz4-1
  74. sudo apt-get install build-essential
  75. sudo apt-get install libfuse-dev fuse pkg-config # optional, for FUSE support
  76. In case you get complaints about permission denied on ``/etc/fuse.conf``: on
  77. Ubuntu this means your user is not in the ``fuse`` group. Add yourself to that
  78. group, log out and log in again.
  79. Fedora / Korora
  80. +++++++++++++++
  81. Install the dependencies with development headers::
  82. sudo dnf install python3 python3-devel python3-pip python3-virtualenv
  83. sudo dnf install openssl-devel openssl
  84. sudo dnf install libacl-devel libacl
  85. sudo dnf install lz4-devel
  86. sudo dnf install fuse-devel fuse pkgconfig # optional, for FUSE support
  87. Mac OS X
  88. ++++++++
  89. Assuming you have installed homebrew_, the following steps will install all the
  90. dependencies::
  91. brew install python3 lz4 openssl
  92. pip3 install virtualenv
  93. For FUSE support to mount the backup archives, you need at least version 3.0 of
  94. FUSE for OS X, which is available as a pre-release_.
  95. .. _pre-release: https://github.com/osxfuse/osxfuse/releases
  96. Cygwin
  97. ++++++
  98. .. note::
  99. Running under Cygwin is experimental and has only been tested with Cygwin
  100. (x86-64) v2.1.0.
  101. Use the Cygwin installer to install the dependencies::
  102. python3 python3-setuptools
  103. python3-cython # not needed for releases
  104. binutils gcc-core
  105. libopenssl openssl-devel
  106. liblz4_1 liblz4-devel # from cygwinports.org
  107. git make openssh
  108. You can then install ``pip`` and ``virtualenv``::
  109. easy_install-3.4 pip
  110. pip install virtualenv
  111. In case the creation of the virtual environment fails, try deleting this file::
  112. /usr/lib/python3.4/__pycache__/platform.cpython-34.pyc
  113. .. _pip-installation:
  114. From PyPi / using pip
  115. ~~~~~~~~~~~~~~~~~~~~~
  116. Virtualenv_ can be used to build and install |project_name| without affecting
  117. the system Python or requiring root access. Using a virtual environment is
  118. optional, but recommended except for the most simple use cases.
  119. .. note::
  120. If you install into a virtual environment, you need to **activate** it
  121. first (``source borg-env/bin/activate``), before running ``borg``.
  122. Alternatively, symlink ``borg-env/bin/borg`` into some directory that is in
  123. your ``PATH`` so you can just run ``borg``.
  124. This will use ``pip`` to install the latest release from PyPi::
  125. virtualenv --python=python3 borg-env
  126. source borg-env/bin/activate
  127. # install Borg + Python dependencies into virtualenv
  128. pip install 'llfuse<0.41' # optional, for FUSE support
  129. # 0.41 and 0.41.1 have unicode issues at install time
  130. pip install borgbackup
  131. To upgrade |project_name| to a new version later, run the following after
  132. activating your virtual environment::
  133. pip install -U borgbackup
  134. .. _git-installation:
  135. From Github / using git
  136. ~~~~~~~~~~~~~~~~~~~~~~~
  137. This uses latest, unreleased development code from git.
  138. While we try not to break master, there are no guarantees on anything. ::
  139. # get borg from github
  140. git clone https://github.com/borgbackup/borg.git
  141. virtualenv --python=python3 borg-env
  142. source borg-env/bin/activate # always before using!
  143. # install borg + dependencies into virtualenv
  144. pip install sphinx # optional, to build the docs
  145. pip install 'llfuse<0.41' # optional, for FUSE support
  146. # 0.41 and 0.41.1 have unicode issues at install time
  147. cd borg
  148. pip install -r requirements.d/development.txt
  149. pip install -e . # in-place editable mode
  150. # optional: run all the tests, on all supported Python versions
  151. # requires fakeroot, available through your package manager
  152. fakeroot -u tox
  153. .. note:: As a developer or power user, you always want to use a virtual environment.