[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gpsd-dev] Time for a snap release due to the leapsecond change!

From: Greg Troxel
Subject: Re: [gpsd-dev] Time for a snap release due to the leapsecond change!
Date: Sun, 01 Jul 2012 11:15:43 -0400
User-agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.4 (berkeley-unix)

"Eric S. Raymond" <address@hidden> writes:

> Greg Troxel <address@hidden>:
>> As much as I don't like having packages download bits, it might be nice
>> to have a leap second file and a way to grab the new one from usno, so
>> that release and leap second update can be decoupled.  But it may not be
>> worth the effort, since it seems to only affect a few devices which are
>> arguably broken by design.
> The obvious problem case is Evermore chips in binary mode, which report
> only GPS week and TOW for time but never the leap-second offset.  There
> aren't any other devices where this is known to be a problem, but that
> qualifier "where this is known" worries me. 

So perhaps it's not worth a lot of effort.

> Your idea is potentially interesting, but not something I want to try
> shipping without time for thought and testing.  I think it's best to apply
> the simple stopgap fix now, then consider more permanent solutions at
> leisure.

Agreed - I didn't mean to suggest something immediate, just a thought
for the future, maybe before the next leap second.

Attachment: pgpV7BOe962HP.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]