13,208
edits
m (Update for 1.12.2 release) |
(→Using pip (generic method): No need to add a separate anchor to link to a section. Use <Article>"#"<Section>, like FFGo#Using pip (generic method) instead) |
||
(7 intermediate revisions by one other user not shown) | |||
Line 3: | Line 3: | ||
| title = FFGo | | title = FFGo | ||
| image = FFGo LPMA-apt-tooltip-and-FG-cmd.png | | image = FFGo LPMA-apt-tooltip-and-FG-cmd.png | ||
| alt = Screenshot of FFGo 1.12. | | alt = Screenshot of FFGo 1.12.3 | ||
| developedby = Florent Rougon | | developedby = Florent Rougon | ||
| type = Graphical launcher for FlightGear | | type = Graphical launcher for FlightGear | ||
| initialrelease = 1.0.0 (Aug 21, 2015) | | initialrelease = 1.0.0 (Aug 21, 2015) | ||
| latestrelease = 1.12. | | latestrelease = 1.12.5 (March 29, 2017) | ||
<!-- simplifying Python3 to Python for the category to work correctly--> | <!-- simplifying Python3 to Python for the category to work correctly--> | ||
| writtenin = Python | | writtenin = Python | ||
| writteninversion = 3 | | writteninversion = 3 | ||
| os = Unix-like (incl. Linux), Windows, MacOS X | | os = Unix-like (incl. Linux), Windows, MacOS X | ||
| developmentstatus = Active (as of | | developmentstatus = Active (as of March 2017) | ||
| website = http://frougon.net/projects/FFGo/ | | website = http://frougon.net/projects/FFGo/ | ||
| license = {{wikipedia|WTFPL#Version 2|WTFPL version 2|noicon=1}} | | license = {{wikipedia|WTFPL#Version 2|WTFPL version 2|noicon=1}} | ||
Line 538: | Line 538: | ||
deb-src http://frougon.net/debian-ffgo unstable main</pre> | deb-src http://frougon.net/debian-ffgo unstable main</pre> | ||
<p>(replace < | <p>(replace <i>unstable</i> with <i>stretch</i> if you are using Debian 9, also known as <i>stretch</i>)</p> | ||
</li> | </li> | ||
<li>'''Third step: update the <tt>apt</tt> package list''' | <li>'''Third step: update the <tt>apt</tt> package list''' | ||
Line 560: | Line 560: | ||
<li><tt>python3-geographiclib</tt> if available for your distribution (i.e., after <i>jessie</i>), for better geodesic calculations.</li></ul> | <li><tt>python3-geographiclib</tt> if available for your distribution (i.e., after <i>jessie</i>), for better geodesic calculations.</li></ul> | ||
<p>In other words, if you are using '' | <p>In other words, if you are using Debian ''stretch'' or later, you can run:</p> | ||
<pre>apt-get install ffgo python3-pil.imagetk geographiclib-tools python3-geographiclib</pre> | <pre>apt-get install ffgo python3-pil.imagetk geographiclib-tools python3-geographiclib</pre> | ||
Line 630: | Line 630: | ||
Just as for the [https://pip.pypa.io/ pip] command explained above, think of <code>/usr/bin/python3.4 -m venv</code> as the name of a program (it just runs the main function of the Python <tt>venv</tt> module). In the above command, you can freely choose the <venv-dir> directory. It is just a directory that is going to contain the newly-created virtual environment once this command returns (therefore, you shouldn't have anything inside it before running the command, otherwise that would be messy). | Just as for the [https://pip.pypa.io/ pip] command explained above, think of <code>/usr/bin/python3.4 -m venv</code> as the name of a program (it just runs the main function of the Python <tt>venv</tt> module). In the above command, you can freely choose the <venv-dir> directory. It is just a directory that is going to contain the newly-created virtual environment once this command returns (therefore, you shouldn't have anything inside it before running the command, otherwise that would be messy). | ||
<p> | <p>Note:</p> | ||
<blockquote> | <blockquote> | ||
<p>Some systems may provide executables named <tt>pyvenv-3.4</tt> or similar. For instance, on Debian, <tt>/usr/bin/pyvenv-3.4</tt> is a “shortcut” for <code>/usr/bin/python3.4 -m venv</code>. Thus, one may type:</p> | |||
<syntaxhighlight lang="shell" enclose="div"> | <syntaxhighlight lang="shell" enclose="div"> | ||
Line 639: | Line 639: | ||
<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> | ||
</blockquote> | </blockquote> | ||