Anders Gidenstam wrote:
> On Sun, 15 Jan 2012, Martin Spott wrote:
>
>> 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 ;-)
>
> Well, from looking at the FlightGear source code it appears that FG_HOME
> has been $HOME/.fgfs by default since the first occurence of the
> string "FG_HOME" in the source (Jan 29 2005 in commit
> 4ffb6c0fe9e36ec74c912eec9a64868171577e9e).
>
> If the Manual says something else it might be time to update it. :)
I'm not claiming that The Manual is correct in every aspect, I'm not
even sure what the manual currently says about $FG_HOME, but I know
from gathering information _for_ the manual what $FG_HOME is meant to
be - as written above.
Just look at it from the other side: Anybody implementing his private
assumptions about $FG_HOME into some place of the code (I haven't
looked at the respective commit) does not by definition change the
overall intention of what $FG_HOME is supposed to represent.
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
