Re: ✘GPS WKRO workaround

[Fred Wright]

On Fri, 6 Dec 2019, Gary E. Miller wrote:

[...]
> Anything else that shold be addressed before next release?

There are two regressions since the last release that I'm aware of:

1) The C++ build breakage related to timespec_str.  I already have a 
tentative fix for that, but just as I was about to test it, I ran into a 
disk-space issue for my VMs, which I'm in the process of sorting out.  The 
whole C++ area is pretty much a mess, but at least this can make it no 
worse than it used to be.

2) The rename of the altitude field has an interoperability issue with 
other GPSD versions.  The client and server can be on different machines, 
and not necessarily the same version.  At least one direction should be 
fixable with a bit of fallback code.

Fred Wright