Torsten Dreyer wrote: > Hi, > > what is our current policy for updates to nav.dat? Do we commit changes > to the binary gzip'ed file or do we have a central repository for the > data? > > Would it make sense to have the unzip'ed file in git and zip it for the > release in "make dist"? > > Torsten >
Hi Torsten, given the fact that some updates in nav.dat would make sense and the fact that git will store (and compress) changes to textfiles much better than those to binary ones, I like your move a lot. Especially as it would make it easier for everyone to see the changes in GIT. In this case it would make sense to unpack apt.dat, too, as many changes need to be done to the two files (ILS changes i.e.) The central repository would be Robin Peels xplane database, which still contains nav.dat files compatible with FG. BUT as they depend on a certain apt.dat version we can't just copy them over as a whole. In the future, when our scenery is created with apt.dat 850 data, we still have to keep one apt.dat file, as it has to match the distributed scenery. HTH Chris ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
