Am 07.02.2012 21:34, schrieb Curtis Olson: > The main reason for a version check between the binary and the data is > that we often make parallel changes to both (similar reason why we do a > simgear minimum version check when compiling flightgear.) If there are > version mismatches, things could break or act in weird or unexpected ways. > > A launcher might not be in the same category unless you use options that > change between versions (this is possible, but happens a lot less often > than other sorts of changes.)
Right. Not sure what Yves' original intention were. I referred to the basic check if the "version" file is there _at all_ - such a check seems useful for a launcher. Restricting a launcher to a specific version number inside the file indeed wouldn't be a good idea. At least I'd like to keep using the same launcher for a variety of fgfs versions - 2.5.0, 2.6.0, 2.7.0 :). cheers, Thorsten ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
