Hi All, All the new aircraft etc in FGFS is very impressive :-)
But this is starting to add for me anyway an unacceptable time burden on statying current. i.e. I am trying to debug a Cloud3D crash which appeared today and assuming that it was probably something in the base files that changed I am did a cvs up for fgfsbase. This took over 45 minutes on my 56k dialup. :-( I am wondering if it would be worthwhile to split the fgfsbase CVS into two parts. 1: Those files distributed in the fgfsbase tarball < fgfsbase > 2) Those files not distributed. < fgfsextra > This seems a logical separation and should allow finer granularity on what one updated. i.e within the fgfsextra CVS one could selectively update directories. Note this isn't really feasable with the current setup in that you need the toplevel CVS files to run FGFS I realize that this would take a bit of work to setup but as FGFS gets more 'extras' this will become a larger problem and require even more work to convert thoughts / flames ?? Norman _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
