FFGo: Difference between revisions

179 bytes added ,  19 March 2016
→‎General idea of the method: Update note about Debian bug #815864, which is now fixed
(→‎Installing FFGo and its dependencies: Format instructions for running FFGo from a Command Prompt as a tip (template); improve wording and presentation)
(→‎General idea of the method: Update note about Debian bug #815864, which is now fixed)
Line 588: Line 588:
<p>to obtain the same effect as above: creating a virtual environment in <venv-dir> based on the Python interpreter <tt>/usr/bin/python3.4</tt>. Thanks to shell command history, using <code>/usr/bin/python3.4 -m venv</code> is not much of a problem, and since this makes it quite clear which Python interpreter is going to be used, I'll favor this syntax here rather than the shorter syntax based on <tt>pyvenv-3.4</tt>.</p>
<p>to obtain the same effect as above: creating a virtual environment in <venv-dir> based on the Python interpreter <tt>/usr/bin/python3.4</tt>. Thanks to shell command history, using <code>/usr/bin/python3.4 -m venv</code> is not much of a problem, and since this makes it quite clear which Python interpreter is going to be used, I'll favor this syntax here rather than the shorter syntax based on <tt>pyvenv-3.4</tt>.</p>
</li>
</li>
<li><p>Currently (March 1st, 2016), this step doesn't work on Debian
<li>
<i>unstable</i>—there is a reason it is called <i>unstable</i>—because the
  <p>
<tt>python3-venv</tt> package is broken (cf.
    If you use Debian <i>unstable</i>, be sure to have the
[https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815864 bug #815864]). See
    <tt>python3-venv</tt> package in version 3.5.1-8 or newer (the fixed
[http://forum.flightgear.org/viewtopic.php?f=18&t=27054&p=278031#p278031 this message on the FlightGear forum] for possible workarounds.</p>
    <tt>python3-venv</tt> package was uploaded on March 18, 2016). With
    earlier versions, creating a a virtual environment
    [https://bugs.debian.org/815864 could fail]. Workarounds have been given in
    [http://forum.flightgear.org/viewtopic.php?f=18&t=27054&p=278031#p278031 this message on the FlightGear forum],
    but the simplest thing to do now is to just make sure that your
    <tt>python3-venv</tt> package is up-to-date.
  </p>
</li>
</li>
</ul>
</ul>
377

edits