On Wed, 2011-01-26 at 20:53 +0100, Bertrand Coconnier wrote: > Let's take an example : let's say I develop some code for JSBSim to > take into account FG ground material in the landing gears friction > forces. For that, I need to modify both JSBSim library *and* > FlightGear glue code. So I will submit a patch to JSBSim (for the > friction calcs) and another patch to FlightGear (to give JSBSim access > to FG material data). The patch for FG glue code cannot be applied > readily : first JSBSim needs to be patched and then copied in > FlightGear (or otherwise FG compilation will fail). Once JSBSim last > revision is copied in FlightGear the second part of the patch must be > committed immediately in FlightGear (otherwise FG compilation will > fail). And then the patched glue code will be copied back in JSBSim. > Notice that the patch can be applied at any moment in JSBSim, even 1 > month or 1 year after its submission. On the other hand, some tight > synchronization is needed on the FlightGear side if you don't want FG > compilation to break. Do you think such a process is sustainable ? I > don't.
While it's a valid point I don't see it being as big as a problems as you seem to do. First of all the former situation wasn't ideal either and secondly you could put out a git merge request for the particular changes. Projects like OpenEagles seems to handle this well and so can FlightGear I believe. Erik ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
