On Friday 22 August 2003 9:05 am, Norman Vine wrote: > 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.
I was aware of this becoming an issue at some point when I was doing the base CVS. IMO, the best way to handle it is each plane should be it's own module, then there should be a base package tagged that includes just the basic C172, and another module that is the basic plane & extra modules. > > 1: Those files distributed in the fgfsbase tarball < fgfsbase > > 2) Those files not distributed. < fgfsextra > > I'm still rolling releases of the base package. At one point I was doing that. > 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'm out of touch at this point, but "extra" planes could be stored outside the main tree so cvs up wouldn't update everything and one wouldn't have to give it commands to change the target module. Do we still have the --aircraft-directory option? could it take multiple paths as an argument? > > 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 ?? > This is because unlike other sims everybody that develops planes for FGFS can get them included. It's not a problem for me. It wouldn't be hard to tag things like I described, but it would mean some extra work on the user end to sync with the new paradigm. > Norman > > _______________________________________________ > Flightgear-devel mailing list > [EMAIL PROTECTED] > http://mail.flightgear.org/mailman/listinfo/flightgear-devel _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
