Melchior FRANZ wrote:
* Curtis L. Olson -- Monday 14 November 2005 15:12:
Let's stick with .../.../Scenery/[Terrain|Objects] on all platforms
please. Individuals are welcome to call it whatever they want on their
system and use the --fg-scenery= option to point to their favoritely
named
--- Curtis L. Olson [EMAIL PROTECTED] wrote:
Melchior FRANZ wrote:
Maybe I missed something, but as far as I've understood this thread
is not about renaming $FG_ROOT/Scenery/.
Well ... it could be :)
My aim is to write a section in the Gettings Started Guide so that a new
user can set up
On Monday 14 November 2005 16:06, Buchanan, Stuart wrote:
I'm groping in the dark here as I'm not familiar with terrasync. Am I
correct in thinking that someone using terrasync should have their
terrasync data in a different directory from their directly-downloaded
10x10 scenery?
If so, is
Melchior FRANZ wrote:
This dir doesn't exist. There's no such thing as $FG_ROOT/data/.
Of course there is. :-)
$FG_ROOT/source/
$FG_ROOT/data/
$FG_ROOT/data/Aircraft/
$FG_ROOT/data/Scenery/
This is the prefered structure ...
Regards,
Curt.
--
Curtis Olson
Buchanan, Stuart wrote:
--- Curtis L. Olson [EMAIL PROTECTED] wrote:
Melchior FRANZ wrote:
If so, is the convention to name the directories as follows:
$FG_ROOT/data/Scenery - standard SF bay scenery included in base package
$FG_ROOT/Scenery - scenery downloaded in 10x10 chunks
Curtis L. Olson wrote:
Melchior FRANZ wrote:
This dir doesn't exist. There's no such thing as $FG_ROOT/data/.
Of course there is. :-)
$FG_ROOT/source/
$FG_ROOT/data/
$FG_ROOT/data/Aircraft/
$FG_ROOT/data/Scenery/
Curt, this does not necessarily work. Apparently you have been
--- Martin Spott [EMAIL PROTECTED] wrote:
Buchanan, Stuart wrote:
--- Curtis L. Olson [EMAIL PROTECTED] wrote:
Melchior FRANZ wrote:
If so, is the convention to name the directories as follows:
$FG_ROOT/data/Scenery - standard SF bay scenery included in base
package
Melchior FRANZ wrote:
* Curtis L. Olson -- Monday 14 November 2005 16:34:
Melchior FRANZ wrote:
This dir doesn't exist. There's no such thing as $FG_ROOT/data/.
Of course there is. :-)
Sheesh. I resign. :-}
$FG_ROOT/source/
$FG_ROOT/data/
Martin Spott wrote:
Curt, this does not necessarily work. Apparently you have been
misunderstood by several people for a long time. This makes the
topic really funny :-)
Looking at the facts, 'fgfs' actually does find the aircraft model,
when data/ resides _below_ $FG_ROOT, but it does _not_
Buchanan, Stuart wrote:
OK, so I think I'd like to suggest that for the Getting Started Guide we
suggest for Windows
whatever_path_to_FG/data/Scenery
whatever_path_to_FG/Scenery
and for *nix
$FG_ROOT/Scenery
/usr/share/FlightGear/Scenery
I'm expecting that *nix users will be familiar enough
Melchior FRANZ wrote:
* Curtis L. Olson -- Monday 14 November 2005 16:54:
This is a hopeless conversation because everyone wants to do it
different and there are so many possibilities.
We are talking about different things. You talk about the organization
of source and data in your
On Monday 14 November 2005 16:58, Curtis L. Olson wrote:
We can suggest different default locations of $FG_ROOT for different
systems, but below $FG_ROOT we should use the same structure for all
platforms.
Curt.
Then we should definitely officially use /usr/local/games/flightgear/
or
Oliver C. wrote:
To make use of /usr/local/games/flightgear/ or /opt/flightgear/ by
default we
should change the configure script accordingly.
As FlightGear is a self contained package (including binaries, libs and
data) it belongs to /opt/flightgear according to the FHS. Which would
also
Oliver C. wrote:
Then we should definitely officially use /usr/local/games/flightgear/
or /opt/flightgear/ as $FG_ROOT on unix systems.
I don't understand why the hell people should want to use
/usr/local/games/ for FlightGear ?
Just curious,
Martin.
--
Unix _IS_ user friendly -
On Monday 14 November 2005 18:05, Martin Spott wrote:
Oliver C. wrote:
Then we should definitely officially use /usr/local/games/flightgear/
or /opt/flightgear/ as $FG_ROOT on unix systems.
I don't understand why the hell people should want to use
/usr/local/games/ for FlightGear ?
That's
Martin Spott wrote:
Oliver C. wrote:
Then we should definitely officially use /usr/local/games/flightgear/
or /opt/flightgear/ as $FG_ROOT on unix systems.
I don't understand why the hell people should want to use
/usr/local/games/ for FlightGear ?
The slackware package puts the binaries
Oliver C. wrote:
Seriously, i can live with both directories.
/opt/flightgear is fine too.
Great - should we focus on this one for documentation purpose ?
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
Buchanan, Stuart wrote:
--- Martin Spott [EMAIL PROTECTED] wrote:
OK, so I think I'd like to suggest that for the Getting Started Guide we
suggest for Windows
whatever_path_to_FG/data/Scenery
whatever_path_to_FG/Scenery
and for *nix
$FG_ROOT/Scenery
/usr/share/FlightGear/Scenery
But why
--- Melchior FRANZ [EMAIL PROTECTED] wrote:
Both are wrong, according to the FHS, and to common sense. The right
path
is /usr/local/share/ ... and guess what? It's already the default. So,
What is FHS?
So for consistency in the docs (and ignoring power users like the people
who inhabit this
On Monday 14 November 2005 19:07, Buchanan, Stuart wrote:
--- Melchior FRANZ [EMAIL PROTECTED] wrote:
Both are wrong, according to the FHS, and to common sense. The right
path
is /usr/local/share/ ... and guess what? It's already the default. So,
What is FHS?
It's the unix Filesystem
On Monday 14 November 2005 18:47, Melchior FRANZ wrote:
* Oliver C. -- Monday 14 November 2005 18:46:
[/usr/local/games/FlightGear or /opt/flightgear]
Seriously, i can live with both directories. /opt/flightgear is fine too.
Both are wrong, according to the FHS, and to common sense. The
On Mon, 14 Nov 2005 16:42:24 +0100, Oliver wrote in message
[EMAIL PROTECTED]:
I suggest to remove the SF bay scenery in the corresponding 10x10
scenery file.
This allows us to place the SF bay, which comes allready with the base
package, in the main scenery folder like all the other 10x10
22 matches
Mail list logo
