From: Martin S. <Mar...@mg...> - 2012-01-15 17:06:07
|
Anders Gidenstam wrote: > AFAIK ${FG_HOME} defaults to $HOME/.fgfs/ on unix-like systems [...] As far as I remember ${FG_HOME} predates ${HOME}/.fgfs/ by approx. the half of FlightGear's lifetime. According to my understanding, from the information I retrieved for writing parts of The Manual (_before_ ${HOME}/.fgfs/ was introduced), ${FG_HOME} is supposed to point to FlightGear's install directory, thus it's the same as the install prefix you enter for Autoconf/CMake. If you're having everything of FlightGear installed below a single directory, containing "bin/" for the binaries and "fgdata/" for the Base Package (or just "data/" before we switched to GIT), then ${FG_HOME} is the variable which is queried for finding the Base Package at runtime, because it is supposed to reside in "${FG_HOME}/fgdata/" by definition unless you specify a different directory by setting ${FG_ROOT} As a consequence, ${FG_HOME} is supposed _not_ to be writeable. If it doesn't work this way, I think it's a bug ;-) Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- |