406
edits
$FG HOME: Difference between revisions
Jump to navigation
Jump to search
m
Rant Mark II
m (This is a rant. Read it. Feel free to reverse it. But only do so if you want your software controlling you and your hardware environment.) Tag: Reverted |
m (Rant Mark II) Tag: Reverted |
||
| Line 7: | Line 7: | ||
<code>$FG_HOME</code> is normally used to refer to the operating system specific location for some settings/folders. Its default value is determined by the <code>fgfs</code> binary during startup and is a directory that varies with the operating system supported by FG (Windows, OS X and Linux). ''It is [https://sourceforge.net/p/flightgear/mailman/message/34995089/ highly recommended] to rely on the default value (i.e., not setting <code>$FG_HOME</code> yourself in any way), unless you Really Know What You Are Doing™.'' '''''Why is that?! What if one does not want fgfs to glut their $HOME folder with a massive amount of data (13G ~/.fgfs/TextureCache/)? Why is it so difficult to select another location? Why do developers think hiding the internals of a programme from the user is a good thing? This project claimed to be a simulator. Now it is a mere game. The qt launcher looks like an app. We do not want apps, we liked fgrun. Even specifiying --prop:sim/fg-home=$some_path does not prevent fgfs from clogging the $HOME folder.''''' | <code>$FG_HOME</code> is normally used to refer to the operating system specific location for some settings/folders. Its default value is determined by the <code>fgfs</code> binary during startup and is a directory that varies with the operating system supported by FG (Windows, OS X and Linux). ''It is [https://sourceforge.net/p/flightgear/mailman/message/34995089/ highly recommended] to rely on the default value (i.e., not setting <code>$FG_HOME</code> yourself in any way), unless you Really Know What You Are Doing™.'' '''''Why is that?! What if one does not want fgfs to glut their $HOME folder with a massive amount of data (13G ~/.fgfs/TextureCache/)? Why is it so difficult to select another location? Why do developers think hiding the internals of a programme from the user is a good thing? This project claimed to be a simulator. Now it is a mere game. The qt launcher looks like an app. We do not want apps, we liked fgrun. Even specifiying --prop:sim/fg-home=$some_path does not prevent fgfs from clogging the $HOME folder.''''' | ||
'''''We are aware of the possibility to set the env var. But that is not a userfriendly option. With the transition from fgrun to the qt launcher users have been stripped of the knowledge about the sim's, pardon me, game's, available options. The qt launcher is, in fact, not more userfriendly but more of a user dictation.'''''' | |||
Very advanced users (i.e. power users and developers) who wish to run parallel installs of FlightGear can specify a different <code>$FG_HOME</code> for each install as described below. | Very advanced users (i.e. power users and developers) who wish to run parallel installs of FlightGear can specify a different <code>$FG_HOME</code> for each install as described below. '''''Really?! Where below? Do you have link to that section?!''''' | ||
{{note|The <code>/sim/fg-home</code> property should be considered read-only, for similar reasons why <code>$FG_HOME</code> shouldn't be explicitly set by users.}} | {{note|The <code>/sim/fg-home</code> property should be considered read-only, for similar reasons why <code>$FG_HOME</code> shouldn't be explicitly set by users.}} | ||