installation.rst 6.9 KB

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