Re: [gpsd-dev] leapsecond.cache, git

[Eric S. Raymond]

Greg Troxel <address@hidden>:
> > OK, but under your method, how does the leapsecond update get into the 
> > codebase we ship?
> 
> Someone with commit access copies the new bits into leapsecond.cache.in
> and commits it.   (I don't understand why that seems tricky.)

In other words, the same thing that happens..now?
 
> My complaint is that one randomly ends up with unstaged changes, which
> violates the basic notion that build procedures should treat sources as
> read only.  To me this is far more important than shaving off the last
> 1E-5 that someone who isn't following best practices will have an old
> file.

You randomly end up with unstaged changes at absolute most once per
six months, at IERS update time, in one file. And "git checkout" is a
thing. I'm not seeing a problem here that I think is more important
than promptest possible correctness.
-- 
                <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>

signature.asc
Description: Digital signature