docs: pip-mopidy can now use apt-extensions
This commit is contained in:
parent
f65784e510
commit
74e4d3f9ab
@ -114,11 +114,17 @@ from a regular Mopidy setup you'll want to know about.
|
|||||||
sudo service mopidy status
|
sudo service mopidy status
|
||||||
|
|
||||||
- Mopidy installed from a Debian package can use both Mopidy extensions
|
- Mopidy installed from a Debian package can use both Mopidy extensions
|
||||||
installed both from Debian packages and extensions installed with pip.
|
installed both from Debian packages and extensions installed with pip. This
|
||||||
|
has always been the case.
|
||||||
|
|
||||||
The other way around does not work: Mopidy installed with pip can use
|
Mopidy installed with pip can use extensions installed with pip, but
|
||||||
extensions installed with pip, but not extensions installed from a Debian
|
not extensions installed from a Debian package released before August 2015.
|
||||||
package. This is because the Debian packages install extensions into
|
This is because the Debian packages used to install extensions into
|
||||||
:file:`/usr/share/mopidy` which is normally not on your ``PYTHONPATH``.
|
:file:`/usr/share/mopidy` which is normally not on your ``PYTHONPATH``.
|
||||||
Thus, your pip-installed Mopidy will not find the Debian package-installed
|
Thus, your pip-installed Mopidy would not find the Debian package-installed
|
||||||
extensions.
|
extensions.
|
||||||
|
|
||||||
|
In August 2015, all Mopidy extension Debian packages was modified to install
|
||||||
|
into :file:`/usr/lib/python2.7/dist-packages`, like any other Python Debian
|
||||||
|
package. Thus, Mopidy installed with pip can now use extensions installed
|
||||||
|
from Debian.
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user