Backup_Repos/beets
1
0
Fork 0
mirror of https://github.com/beetbox/beets.git synced 2025-12-26 02:24:33 +01:00
Code Issues Projects Releases Wiki Activity

Slight rewording in docs about SIP

Browse source
This commit is contained in:
Adrian Sampson 2016-10-26 13:40:45 -04:00
parent c4a5dc2436
commit bb9a107c56
1 changed files with 9 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/guides/main.rst
View file

@ -72,7 +72,15 @@ new versions.
Installing on macOS 10.11 and Higher
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Starting with macOS 10.11 (El Capitan), Apple has enabled `System Integrity Protection`_ (SIP), and because of SIP, some installation processes may fail, even with ``sudo``, because they intrude on protected areas of the system (if you've installed python via `Homebrew`_ this probably won't happen since the Python libraries are installed to an unrestricted folder). If this does happen, try installing beets only for the current user by running ``pip install --user beets``. It might also be a good idea to add ``~/Library/Python/2.7/bin`` to your ``$PATH``.
Starting with version 10.11 (El Capitan), macOS has a new security feature
called `System Integrity Protection`_ (SIP) that prevents you from modifying
some parts of the system. This means that some ``pip`` commands may fail with
a permissions error, even when you use ``sudo``. (You probably *won't* run
into this if you've installed Python yourself with `Homebrew`_ or otherwise.)
If this happens, you can install beets for the current user only (sans
``sudo``) by typing ``pip install --user beets``. If you do that, you might want
to add ``~/Library/Python/2.7/bin`` to your ``$PATH``.
.. _System Integrity Protection: https://support.apple.com/en-us/HT204899
.. _Homebrew: http://brew.sh