Re: [Flightgear-devel] Getting Started Guide - Terrain/Objects
Buchanan, Stuart wrote: OK, I'll suggest /var/share/FlightGear/WorldScenery/[Terrain|Objects] for *nix, and FG_ROOT\Scenery\[Terrain|Objects] for Windows. I'm sure you meant /usr/share/FlightGear/... and not /var. Just to clarify, Nine ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Getting Started Guide - Terrain/Objects
Stefan Seifert wrote: I'm sure you meant /usr/share/FlightGear/... and not /var. Makes more sense to me. -- Jon Stockill [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Getting Started Guide - Terrain/Objects
Stefan Seifert wrote: Buchanan, Stuart wrote: OK, I'll suggest /var/share/FlightGear/WorldScenery/[Terrain|Objects] for *nix, and FG_ROOT\Scenery\[Terrain|Objects] for Windows. I'm sure you meant /usr/share/FlightGear/... and not /var. Hehe, I've started a similar discussion twice in the past when I was seeking for an appropriate phrase to put into the manual. The consensus was that we didn't manage to find a consensus :-) Herewith I suggest $FG_ROOT\Scenery\[Terrain|Objects]\ for Windows and $FG_ROOT/Scenery/[Terrain|Objects]/ for Unix, so everyone is free to place their Scenery by choosing an appropriate place for $FG_ROOT. Regards, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Getting Started Guide - Terrain/Objects
On Mon, 14 Nov 2005, Stefan Seifert wrote: Buchanan, Stuart wrote: OK, I'll suggest /var/share/FlightGear/WorldScenery/[Terrain|Objects] for *nix, and FG_ROOT\Scenery\[Terrain|Objects] for Windows. I'm sure you meant /usr/share/FlightGear/... and not /var. I thought /var because of the indeterministic size --- some folks will terrasync only a small local area, some will more... ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Getting Started Guide - Terrain/Objects
Vassilii Khachaturov wrote: On Mon, 14 Nov 2005, Stefan Seifert wrote: Buchanan, Stuart wrote: OK, I'll suggest /var/share/FlightGear/WorldScenery/[Terrain|Objects] for *nix, and FG_ROOT\Scenery\[Terrain|Objects] for Windows. I'm sure you meant /usr/share/FlightGear/... and not /var. I thought /var because of the indeterministic size --- some folks will terrasync only a small local area, some will more... terrasync is another story, which is no problem through giving FlightGear two scenery paths. Additionally no one should run terrasync as root anyway, so it can't write to /var/share/FlightGear. terrasync users should have their own scenery directory in their homes or anywhere their user is able to write. Nine ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Getting Started Guide - Terrain/Objects
On Monday 14 November 2005 15:01, Stefan Seifert wrote: Vassilii Khachaturov wrote: On Mon, 14 Nov 2005, Stefan Seifert wrote: Buchanan, Stuart wrote: OK, I'll suggest /var/share/FlightGear/WorldScenery/[Terrain|Objects] for *nix, and FG_ROOT\Scenery\[Terrain|Objects] for Windows. I'm sure you meant /usr/share/FlightGear/... and not /var. I thought /var because of the indeterministic size --- some folks will terrasync only a small local area, some will more... terrasync is another story, which is no problem through giving FlightGear two scenery paths. Additionally no one should run terrasync as root anyway, so it can't write to /var/share/FlightGear. terrasync users should have their own scenery directory in their homes or anywhere their user is able to write. Nine I agree. User data (like from terrasync) belong to ~./local/share/FlightGear or ~./flightgear/ When using the latter one, we could also start to put the .fgfsrc config file into ~./flightgear/ The preferenced.xml file should also belong there, because it is user specific and the user should allways be able to edit it. A system wide global installation should put the scenery into /usr/share/FlightGear/scenery or /usr/local/share/FlightGear/scenery (for a distribution independent installation) That's what FHS proposes/dictate. If we want to keep consistency like Curt proposes, then we should put everything into /usr/local/games/FlightGear/ The reason is, in /usr/local/games we can have our own directory for everything (data, scripts, binarys etc.,). In /usr/local/games/ there is no need to spread everything around over the system. BTW, an alternative to /usr/local/games would be /opt/ Best Regards, Oliver C. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Getting Started Guide - Terrain/Objects
Hi All, As with 0.9.9 we'll be using the FG scenery DB objects, will the default scenery directory topology be something this Scenery/Terrain/w010n50 Scenery/Objects/w010n50 ? Assuming this is the case - a) Should this be what is mentioned in the Getting Started Guide as the way scenery is installed (I'm happy to make the update) b) Should the binary installers create the Terrain and Objects subdirectories (someone else will have to do this one) From a documentation point of view, I don't want to have to explain two different approaches and the issues with a Terrain subdirectory that can arise, so it would be nice only to have one standard. -Stuart ___ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Getting Started Guide - Terrain/Objects
Hi All, As with 0.9.9 we'll be using the FG scenery DB objects, will the default scenery directory topology be something this Scenery/Terrain/w010n50 Scenery/Objects/w010n50 ? I suggest encouraging 2 directories --- 1 for the static scenery coming with FG, and the other one for the Terrasync DB/Jon's database/ whatever else external source. Melchior has it summed up pretty nicely at http://members.aon.at/mfranz/flightgear/flightgear-howto.html I'd only suggest to have the world scenery under smth like /var/share/FlightGear/WorldScenery (maybe share/games) rather than in the FG_ROOT, to make it more up-to-date with the current FHS. Assuming this is the case - a) Should this be what is mentioned in the Getting Started Guide as the way scenery is installed (I'm happy to make the update) b) Should the binary installers create the Terrain and Objects subdirectories (someone else will have to do this one) The binary installers could also have an option of launching a local terrasync service in a dedicated account with write permission into the world scenery Terrain subdir. From a documentation point of view, I don't want to have to explain two different approaches and the issues with a Terrain subdirectory that can arise, so it would be nice only to have one standard. In some place the difference would have to be explained because of the people that make the upgrade, wouldn't it? Thank you very much for the docu. updates! V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Getting Started Guide - Terrain/Objects
--- Vassilii Khachaturov [EMAIL PROTECTED] wrote: Scenery/Terrain/w010n50 Scenery/Objects/w010n50 ? I suggest encouraging 2 directories --- 1 for the static scenery coming with FG, and the other one for the Terrasync DB/Jon's database/ whatever else external source. Melchior has it summed up pretty nicely at http://members.aon.at/mfranz/flightgear/flightgear-howto.html I'd only suggest to have the world scenery under smth like /var/share/FlightGear/WorldScenery (maybe share/games) rather than in the FG_ROOT, to make it more up-to-date with the current FHS. OK, I'll suggest /var/share/FlightGear/WorldScenery/[Terrain|Objects] for *nix, and FG_ROOT\Scenery\[Terrain|Objects] for Windows. The binary installers could also have an option of launching a local terrasync service in a dedicated account with write permission into the world scenery Terrain subdir. From a documentation point of view, I don't want to have to explaintwo different approaches and the issues with a Terrain subdirectory that can arise, so it would be nice only to have one standard. In some place the difference would have to be explained because of the people that make the upgrade, wouldn't it? I'm guessing that most users upgrading won't be re-reading the Getting Started Guide, so this will be a lower priority. Thank you very much for the docu. updates! It's a pleasure. I find it a nice managable contribution to make. Plus I think good documentation is very valuable. -Stuart ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Getting Started Guide - Terrain/Objects
Additionally no one should run terrasync as root anyway, so it can't write to /var/share/FlightGear. terrasync users should have their own scenery directory in their homes or anywhere their user is able to write. Nine I agree. User data (like from terrasync) belong to ~./local/share/FlightGear or ~./flightgear/ When using the latter one, we could also start to put the .fgfsrc config file into ~./flightgear/ I thought about a dedicated account for terrasync (non-root), with right permissions only to the /var/share/FlightGear/Scenery/Terrain (or WorldScenery/Terrain). ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Getting Started Guide - Terrain/Objects
Vassilii Khachaturov wrote: I thought about a dedicated account for terrasync (non-root), with right permissions only to the /var/share/FlightGear/Scenery/Terrain (or WorldScenery/Terrain). Terragear is sufficiently crude and unrefined and user unfriendly that I think we should leave it out of the getting started guide. We are going to send unsuspecting users down a wild goose chase and they'll be disappointed. We can mention it and forward them to more information, but I think we are asking for a lot of trouble if we try to document it in the getting started guide. For instance, it requires rsync to be installed on your system. Probably ok for most modern linux/freebsd systems, but a big problem for the typical windows user ... and even sun/sgi probably don't have it installed by default. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Getting Started Guide - Terrain/Objects
Terragear is sufficiently crude and unrefined and user unfriendly that I think we should leave it out of the getting started guide. We are going to send unsuspecting users down a wild goose chase and they'll be disappointed. We can mention it and forward them to more information, but I think we are asking for a lot of trouble if we try to document it in the getting started guide. For instance, it requires rsync to be OK. This means that we should suggest $FG_ROOT/... based layout (but with different scenery dirs between the base package and the user-installed additional scenery --- unless we keep the scenery download page SFO tile to be the most up-to-date so that the SFO scenery is no longer nukable), and just have a terrasync pointer. Everything else (per-FHS-distro-flavoured dispersion of things under /opt's /share's /var's etc, suid terrasync etc) actually belongs in another document (not yet written, and needed with a much smaller priority, if at all) documenting the best current practices of fg packagers, so that Debian/Gentoo/RH/win32/... packages have the same shared know-how. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
