Re: will libtai's leap-second table be updated?
Paul Sheer <[email protected]> Thu, 2 Aug 2012 16:05:11 -0500
| Newsgroups | gmane.comp.lib.libtai |
|---|---|
| Message-ID | <CABxOuY8RiiGpk=4_F85z5DOnEQsPr3=41Ey95o-EDA_NTozW6Q@mail.gmail.com> |
--e89a8f838b376a5ebc04c64ec4cb Content-Type: text/plain; charset=ISO-8859-1 > > Bear in mind that any external reference used to track the history of leap > seconds is dependent on some maintainer somewhere keeping that reference > updated. It can be abandoned, taken offline, or forged and you have a > dependency > on trusting that source. I maintain my own copy of leapsecs.txt and update > it > when I read an IERS bulletin notifying me of a new leap second. > > off topic, but one could also say that finding a way to provide such an infrastructure would constitute a "solution", whereas NOT providing such an infrastructure constitutes a "non-solution". The latter being a good description of libtai. Libtai provides millions of years of consistent time format... oh except every 18 months when a leap second occurs, when one has to (cough, sputter) *manually* update the leap-second table. is anyone interested in helping to provide a true Solution to this problem? -paul --e89a8f838b376a5ebc04c64ec4cb Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable <br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"m= argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br> Bear in mind that any external reference used to track the history of leap<= br> seconds is dependent on some maintainer somewhere keeping that reference<br= > updated. It can be abandoned, taken offline, or forged and you have a depen= dency<br> on trusting that source. I maintain my own copy of leapsecs.txt and update = it<br> when I read an IERS bulletin notifying me of a new leap second.<br> <span class=3D"HOEnZb"><font color=3D"#888888"></font></span><br></blockquo= te><div><br><br>off topic, but<br><br>one could also say that finding a way= to provide such an infrastructure would constitute a "solution",= whereas NOT providing such an infrastructure constitutes a "non-solut= ion". The latter being a good description of libtai.<br> <br>Libtai provides millions of years of consistent time format... oh excep= t every 18 months when a leap second occurs, when one has to (cough, sputte= r) *manually* update the leap-second table.<br><br><br>is anyone interested= in helping to provide a true Solution to this problem?<br> <br>-paul<br></div></div><br><br><br><br> --e89a8f838b376a5ebc04c64ec4cb--