RE: [Flightgear-devel] Re:[Flightgear-cvslogs] CVS:data preferences.xml, 1.161, 1.162
Curt wrote: As a project, FlightGear needs to depend on the stable releases of the stuff it depends on, not cvs development trees. That get's to be too big of a mess. Many distributions include the latest stable version of plib, and that is often easier to build. It's ok for developers to use cvs versions of our dependencies, as long as they don't break compatibility with the latest stable version. After about 1 second's consideration, I realized that of course this is the only reasonable policy. Unfortunately, now I remember why I changed to using crease: Martin Spott wrote: Curtis L. Olson wrote: Update of /var/cvs/FlightGear-0.9/releases In directory baron:/tmp/cvs-serv18174 Added Files: FlightGear-0.9.6.tar.gz Log Message: Official source release for v0.9.6 I'm asking just to find out: Do we all agree that it makes much sense to build the upcoming binary releases with a crease-patched version of current PLIB CVS ? I will Erik So we have the situation where at least some of the current binary releases, do not follow this policy. The Windows for one seems to accept the crease token. We speak of Mathias' crease patch, but we should remember that it also produced around 40% increase in performance, certainly for Cygwin. I would not like to go back to the status quo ante, but I realize the very good rationale for it. Regards, Vivian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re:[Flightgear-cvslogs] CVS:data preferences.xml, 1.161, 1.162
Vivian Meazza wrote: So we have the situation where at least some of the current binary releases, do not follow this policy. The Windows for one seems to accept the crease token. The policy is not meant for the binary releases. A binary-release maintainer may even chose to use plib-1.7.3 if he/she wishes to do so. The policy is to make it _work_ with the latest official plib release. We speak of Mathias' crease patch, but we should remember that it also produced around 40% increase in performance, certainly for Cygwin. I would not like to go back to the status quo ante, but I realize the very good rationale for it. The patch has been committed to plib CVS. Now we only (...) need to convince them to release a new stable version. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re:[Flightgear-cvslogs] CVS:data preferences.xml, 1.161, 1.162
Vivian Meazza wrote: So we have the situation where at least some of the current binary releases, do not follow this policy. The Windows for one seems to accept the crease token. Binary releases, by definition, are not meant to be rebuild, so the hassle of collecting patches and making all work is only supported by one volunteer, not the average user that want to compile from scratch. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re:[Flightgear-cvslogs] CVS:data preferences.xml, 1.161, 1.162
Erik Hofman wrote: Vivian Meazza wrote: So we have the situation where at least some of the current binary releases, do not follow this policy. The Windows for one seems to accept the crease token. The policy is not meant for the binary releases. A binary-release maintainer may even chose to use plib-1.7.3 if he/she wishes to do so. The policy is to make it _work_ with the latest official plib release. Now I'm confused. Make what work? We speak of Mathias' crease patch, but we should remember that it also produced around 40% increase in performance, certainly for Cygwin. I would not like to go back to the status quo ante, but I realize the very good rationale for it. The patch has been committed to plib CVS. Now we only (...) need to convince them to release a new stable version. Excellent news, what about the joystick problem? Regards, Vivian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re:[Flightgear-cvslogs] CVS:data preferences.xml, 1.161, 1.162
Vivian Meazza wrote: Erik Hofman wrote: The policy is not meant for the binary releases. A binary-release maintainer may even chose to use plib-1.7.3 if he/she wishes to do so. The policy is to make it _work_ with the latest official plib release. Now I'm confused. Make what work? Sorry, I meant: ... make sure FlightGear will work at least with ... Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re:[Flightgear-cvslogs] CVS:data preferences.xml, 1.161, 1.162
Quoting Vivian Meazza : The patch has been committed to plib CVS. Now we only (...) need to convince them to release a new stable version. Excellent news, what about the joystick problem? not committed yet, but I just asked again on the plib list. -Fred ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS:data preferences.xml, 1.161, 1.162
Melchior FRANZ * Jon Stockill -- Tuesday 30 November 2004 16:39: At 03:47 today. Modified Files: nimitz.ac Log Message: Remove crease tag so that people without custom patched versions of plib can still run FlightGear. :-) Yes, and at ... um ... right *now*: $ cd $FG_ROOT/Models/Geometry/Nimitz/ $ find -name \*.ac|xargs grep crease|wc -l 248 so today's Nimitz has all the creases again. And FWIW: $ cd $FG_ROOT/Aircraft/ $ find -name \*.ac|xargs grep crease|wc -l 890 Sorry guys, I sent today's Nimitz before I realized that Curt was removing crease tokens. Mind you, after all the effort we went to get it in ... I'm a bit confused here. Mathias submitted a patch to plib, and I thought that Wolfram Kuss had uploaded it. What's the problem - NIH (Not Invented Here) or what? I've been using 'crease' for a month or so now - The Spitfire/Seafire also uses it. It's absolutely no problem for me to remove it, but it seems a shame since it definitely improves appearance. Regards, Vivian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS:data preferences.xml, 1.161, 1.162
On Tue, 30 Nov 2004 18:40:53 -, Vivian Meazza [EMAIL PROTECTED] wrote: Sorry guys, I sent today's Nimitz before I realized that Curt was removing crease tokens. Mind you, after all the effort we went to get it in ... I'm a bit confused here. Mathias submitted a patch to plib, and I thought that Wolfram Kuss had uploaded it. What's the problem - NIH (Not Invented Here) or what? 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. By the way, are you certain now that the crease patch is in the plib CVS? Since the loaders are not an integral part of the plib core, one alternative would be to maintain our own AC3D loader in FlightGear, based on the plib one. All the best, David -- http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS:data preferences.xml, 1.161, 1.162
Vivian Meazza wrote: Sorry guys, I sent today's Nimitz before I realized that Curt was removing crease tokens. Mind you, after all the effort we went to get it in ... I'm a bit confused here. Mathias submitted a patch to plib, and I thought that Wolfram Kuss had uploaded it. What's the problem - NIH (Not Invented Here) or what? I've been using 'crease' for a month or so now - The Spitfire/Seafire also uses it. It's absolutely no problem for me to remove it, but it seems a shame since it definitely improves appearance. As a project, FlightGear needs to depend on the stable releases of the stuff it depends on, not cvs development trees. That get's to be too big of a mess. Many distributions include the latest stable version of plib, and that is often easier to build. It's ok for developers to use cvs versions of our dependencies, as long as they don't break compatibility with the latest stable version. Regards, Curt. -- Curtis Olsonhttp://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
