Hi, On Tuesday 04 September 2007 20:41, Andy Ross wrote: > > The goal here, I will point out yet again, isn't to decide how best to > develop plib, but to decide how best to get it built > under windows for a FlightGear release. I'd argue that > building our released version against an inconsistent library > dependency constitutes significantly *worse* form than tolerating some > const-incorrectness that has already been vetted out on other > platforms. >
While I appreciate everybody's input into this discussion, I would like to take this opportunity to remind everybody that indeed, the discussion here is not how improve plib code, but how to deal with the existing plib release, within the confines of FlightGear's release policy. Just to remind everybody, here is the situation we're dealing with. FlightGear has a dependency on plib 1.8.4. To the best of my knowledge, we have even received patches depending on SVN-only plib features, but these haven't been incorporated into the program yet. Last week, I found that plib doesn't compile anymore using gcc 4.1.2, although plib SVN does. Olaf has reported compilation problems for MSVC as well. So the main question is: Do we want to stick to our current requirement of building against the plib 1.8.4 release, or do we want to try and require a later build, one way or the other? Arguments in favor of keeping 1.8.4. are. - It's the latest official release - Plib development has quieted down considerably. What are our chances of getting a new release? - Maintaining the 1.8.4 requirement isn't much of a deal, because most linux distributions ship a (patched) version anyway. Arguments in favor of abandoning 1.8.4 are - It doesn't compile on some systems (gcc 4.2.1, latest MSCV) - It frees up some restrictions on the current FlightGear feature set. To me, the most obvious course of action seems to be the following: - People wishing to improve plib code make an effort to get their patches into plib (I'm sure there are still some people working on plib. IIRC John Fay and Bram Stolk have been very cooperative in the past to get patches included). - We request a new release of plib, prior to the next FlightGear release. We've had a good working relationship with plib in the past, and have coordinated releases this way before, so who knows. - If plib does manage to do a new release, we use that one, if not we stick to the current 1.8.4 requirement for this release. Ideally, plib build patches would be in SVN. If we need to stick to plib 1.8.4. we should add a few lines of documentation into the README.plib files to note that and point people to plib SVN. - If we still don't have a new plib version by time of the release following this one, we should consider incorporating the relevant plib files into Flight/SimGear. Cheers, Durk ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
