Avoiding multiple downloads of FGData on Linux: Difference between revisions

Jump to navigation Jump to search
m
small corrections and clearer wording.
m (added wip)
m (small corrections and clearer wording.)
 
Line 17: Line 17:
== The main ideas ==
== The main ideas ==
* You'll need one directory for each separate FlightGear version you want to build.
* You'll need one directory for each separate FlightGear version you want to build.
* You will need a FlightGear directory that matches the version you built
* You will need a FlightGear fgdata directory that matches the version you built
* You can use a single downloaded fgdata for everything using git worktrees.
* You can use a single cloned fgdata for everything using git worktrees.
* If you are building more than one version of flightgear, install/flightgear is not a particularly good location for the main git archive.
* If you are building more than one version of flightgear, install/flightgear is not a particularly good location for the main fgdata git archive.
* fgdata normally lives as a sub-directory in <code>install/flightgear/  There is no rule that says it has to stay there.</code>
* fgdata normally lives as a sub-directory in <code>install/flightgear/  There is no rule that says it has to stay there.</code>
* Once it exists, <code>install/flightgear/fgdata</code> can moved to a safe location and replaced by a symbolic link to that location.  The reason for doing this is that you may at some point want to remove your install directory and completely rebuild it.  Having fgdata in a "safe" location prevents it from being deleted.  You'll just have to recreate the install/flghtgear path and re-create the symbolic link before proceeding with your rebuild.
* Once it exists, <code>install/flightgear/fgdata</code> can moved to a safe location and replaced by a symbolic link to that location.  The reason for doing this is that you may at some point want to remove your install directory and completely rebuild it.  Having fgdata in a "safe" location prevents it from being deleted.  You'll just have to recreate the install/flghtgear path and re-create the symbolic link before proceeding with your rebuild.
* The git worktree feature can be used to create multiple copies of fgdata with a specific version of fgdata checked out for each worktree.  This avoids the necessity of re-downloading fgdata for each variant of flightgear you build.  Having fgdata in that "safe" location is a good idea if you are going to use this feature.
* The git worktree feature can be used to create multiple additional copies of fgdata with a specific version of fgdata checked out for each worktree.  This avoids the necessity of re-downloading fgdata for each variant of flightgear you build.  Having fgdata in that "safe" location is a good idea if you are going to use this git feature.


== Technical points and command examples (need example for git worktree) ==
== Technical points and command examples (need example for git worktree) ==
936

edits

Navigation menu