|
From: | Urs Liska |
Subject: | Re: Next round on frescobaldi dependencies |
Date: | Mon, 1 Jan 2018 03:01:04 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 |
Am 01.01.2018 um 00:26 schrieb Andrew
Bernard:
There is an ambiguity that really should be clarified. The two custom modules that are required are: Both don't have Python 3 in their name, and correctly so, as both
work with both Python2 and Python3. However, for use with
Frescobaldi they have to be used with Python3. That is: when
installing through the distribution's package manager the packages
with python3 in their name have to be used, and when installed
with pip pip3 has to be used.
This is not true.
Actually I have installed Frescobaldi on two computers with freshly installed Ubuntu 17.10. On both computers I installed it from the Git repository (exactly following the instructions on https://github.com/wbsoft/frescobaldi/wiki/Running-Frescobaldi-3-From-Source-Git-(Linux)) *and* from the Ubuntu repository. The difference was only the order. When I first installed the frescobaldi package with apt all dependencies were already met so I didn't have to install them separately for the Git repository version.
From my latest experience the install on the Github Wiki page *is* clean, clear, understandable and manageable. It works on Ubuntu 17.10, Debian 9, and Debian 10 without any issues. I agree that the instructions on frescobaldi.org/download are suboptimal. And I have never tried out the approach of downloading a release archive and using setup.py. Urs
|
[Prev in Thread] | Current Thread | [Next in Thread] |