Imho the right solution here is to file a bug against gpsd. On the announce list of gpsd is no information whatsoever that they are going to break the API - and this breakage happens between two minor versions going from 2.90 to 2.92.
It is good habit in the open source world to have a major version jump when the API is going to break, otherwise it introduces a pain in the neck for users and deveolpers the like. TangoGPS uses an gpsd API that has been around for years and the fact that ESR right out of the blue decides he doesn't want people to use it but go with his libgpsd is a rather void argument, especially with regard to the fact that libgpsd has been very buggy just two years ago. The right thing to do is to keep the gpsd API prior 2.91 around and afterwards have two gpsd, a gpsd2 package and a gpsd3 package. Concerning the patch from Timo: should work as a quick fix. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
