Vivian Meazza wrote:

Martin Spott


No, it's just a matter of stability. We don't want FlightGear
releases to have to depend on prerelease CVS versions of plib, so we
have to wait until the next plib official release.


I'm not convinced that this actually is the point. FlightGear has a
history of depending on a moving PLIB CVS target - Curt has 'convinced'
Steve Baker more than once to issue a PLIB release right before the
next FlightGear release. My "custom patched versions of plib"-package
is far more stable than PLIB CVS trees that have been mandantory many
times in the past - it even carries a time stamp :-)



So it is, and it works with Cygwin.



[...] By the way, are
you certain now that the crease patch is in the plib CVS?


This is the key point: PLIB folks ("core developers") typically don't
feel much urge to commit a patch that they didn't invent themselves or
that servers their own purpose. Steve decided that he didn't have much
use for Mathias' patch so no one actually bothered to commit,




As I thought - NIH. I'm underwhelmed. So where do we go from here - do our
own loaders? Maintain our own version of PLIB?



Don't forget we are all open-source developers here. The plib guys are volunteers just like us. It's pretty easy to be critical and jump ship (so to speak.) It's harder to live with each other and work towards the common good of everyone ... especially with the weird characters that show up on the open-source scene.


We all are busy. Steve is extremely busy. It doesn't hurt to follow up on these things (more than once if needed.) If done in a "sensitive" way, you can usually accomplish reasonable things with reasonable people.

Just keep in mind that we are all volunteers, all have day jobs, many of us have families, we can't all sit and monitor the FG or plib mailing lists 24/7 and drop everything to address every issue that comes up immediately when it comes up.

And also, please be aware that with the volume of mail that most of us get, if we can't do something right away (which is often/usually the case) the email quickly gets buried beneath a flood of newer requests and problems. I'm always waiting for that lull in the action which would allow me to go back through my inbox(s) and address some of the backlog, but such a lull never (or rarely) happens.

Perhaps as a direct suggestion to the immediate issue of the crease patch, we should get more FG people onboard as plib contributors with cvs access so we can make direct contributions and get this fixed?

Regards,

Curt.

--
Curtis Olson        http://www.flightgear.org/~curt
HumanFIRST Program  http://www.humanfirst.umn.edu/
FlightGear Project  http://www.flightgear.org
Unique text:        2f585eeea02e2c79d7b1d8c4963bae2d


_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to