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?
Regards,
Vivian
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
