Arnt Karlsen wrote:
On Sun, 12 Jan 2003 11:03:21 +1100, Geoff Reidy <[EMAIL PROTECTED]> wrote in message <[EMAIL PROTECTED]>:
..yeeha! I was going to write something like this, thanks! Neat job! :-)If you've got plib, SimGear, FlightGear, and fgfsbase installed from cvs you can use this script to keep it up to date: http://home.pacific.net.au/~greendog/flightgear/fgupdate
Glad you like it :)
..a wee policy nit: This _is_ where we (FG) wanna drop in the FG family cvs trees? : "PLIB_DIR=~/games/flightgear/plibNot quite sure what you mean. This script is only useful once you've already checked out all the sources from cvs. Just removes the routine from keeping them up to date.
SIMGEAR_DIR=~/games/flightgear/SimGear
FLIGHTGEAR_DIR=~/games/flightgear/FlightGear
FGFSBASE_DIR=~/games/flightgear/fgfsbase"
..most FG newcomers on thin metered wires will likely first try a tarball or a binary, when we tell'em "try cvs", we should also help'em minimize the DL by dropping the cvs in somewhere convenient, so their old working binaries are left working while their old source trees are reused when possible.
Decisions of where to drop the cvs sources has to be made at check out time and I'm not too sure how to take the pain out of that operation.
Can you run cvs co or update over the source from a tarball? I seem to remember having trouble doing that, though it was ages ago.
Hope noones offended by me having flightgear under games :)
Geoff
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
