Scripted Compilation on Linux Debian/Ubuntu: Difference between revisions

Jump to navigation Jump to search
→‎Choosing between stable and development versions: Add crossref to the place where --component-branch is presented
(→‎Choosing between stable and development versions: Reduce the scope of the large note and reorder to improve readability)
(→‎Choosing between stable and development versions: Add crossref to the place where --component-branch is presented)
Line 473: Line 473:
| text = next
| text = next
}} branch of the FlightGear repository.
}} branch of the FlightGear repository.
The use of <code>-s</code>, <code>--lts</code> or <code>--old-lts</code> also influences the version of other components you may have selected (this can be overridden using <code>--component-branch</code>, for advanced users).
The use of <code>-s</code>, <code>--lts</code> or <code>--old-lts</code> also influences the version of other components you may have selected (this can be overridden using <code>--component-branch</code> for advanced users—see [[#Component-specific settings|Component-specific settings]]).


{{Note|In a given folder where <tt>download_and_compile.sh</tt> is run, you should normally either always use the <code>-s</code> option, or always use <code>--lts</code>, or always use <code>--old-lts</code>, or always none of these (in other words, stick to the same suite: latest stable, latest LTS, previous LTS or ''next'', consistently accross all components).}}
{{Note|In a given folder where <tt>download_and_compile.sh</tt> is run, you should normally either always use the <code>-s</code> option, or always use <code>--lts</code>, or always use <code>--old-lts</code>, or always none of these (in other words, stick to the same suite: latest stable, latest LTS, previous LTS or ''next'', consistently accross all components).}}
377

edits

Navigation menu