Hi, I understand your point of view.
I think that instead of wait a new release of dependant package (plib, OSG...) we have to indicate the release version necessary for FG/SG building. And we can spread our own package (as plib 1.8.5). In fact, it's the issue of package maintener of FG and SG. Regards, Le vendredi 19 décembre 2008 à 13:54 +0100, Sébastien MARQUE a écrit : > I have no problem compiling and using FG/CVS for years now, but my real > thought is that distributions could not spread the new release until > they won't include plib1.8.5 in their packages bases. > > but if nobody thinks it could be a problem for FG, it will surely not be > one. > > btw, if I remember correctly, it seems that FG needs also osg with a > certain version number too. > > note: my compile script ./compile from the previous link was a bit > outdated (and versionning control not working on this version), I've > just pushed the actual version at the same place for the interested. > > regards > seb > > Martin Spott a ecrit : > > Nicolas wrote: > > > >> To solve this issue, you can download my package : > >> > >> http://www.progweb.com/plib/ > > > > BTW, there's also a package available for Debian Etch on Linux/AMD64: > > > > ftp://ftp.ihg.uni-duisburg.de/FlightGear/PLIB/Debian/ > > > > Martin. > > ------------------------------------------------------------------------------ > _______________________________________________ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Nicolas VIVIEN ------------------------------------------------------------------------------ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
