> Also, the current version of FG needs a newer version of plib than Sarge > provides. What are the ramifications of installing both Deb plib and > CVS plib at the same time?
The big questions are: do you need to *develop* against both the sarge version of plib and the newer plib? and, do you need to use the CVS plib, or will the sid plib suffice? If the answer to the 1st q. is no, then, as long as somebody else doesn't say that the debian plib1.8.4 is too old for the CVS flightgear, try to add an unstable deb-src line to your apt sources list, like this (use your local mirror instead): $ grep unstable /etc/apt/sources.list deb-src http://mirror.hamakor.org.il/pub/mirrors/debian/ unstable main contrib non-free and then, as root, do # apt-get update and then try to build the newer plib (which is already in unstable) as a source package. For this, you need to # apt-get build-dep plib1.8.4-dev Then make sure you don't have the older plib-dev deb package around, e.g., in my case, you had to do # apt-get remove plib1.8.3-dev Now you can safely do # apt-src -i build plib1.8.4-dev Having a current sarge system myself, I have just found that this works. I don't have time to do a CVS build of flightgear at this moment, but if simgear+flightgear are OK with plib1.8.4, this might probably be the best debian-kosher way of doing it (unless, of course, you want to tweak with the plib code itself). Now atop of that you can build simgear+flightgear in /usr/local HTH, Vassilii P.S. As always in such cases, I have preserved a script of the session on my system, to compare with yours if it doesn't work for you. _______________________________________________ Flightgear-users mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-users 2f585eeea02e2c79d7b1d8c4963bae2d
