[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gpsd-dev] [PATCH 2/3] leapsecond.py: set a socket timeout for slow
From: |
Greg Troxel |
Subject: |
Re: [gpsd-dev] [PATCH 2/3] leapsecond.py: set a socket timeout for slow servers. |
Date: |
Thu, 31 Oct 2013 19:20:12 -0400 |
User-agent: |
Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.4 (berkeley-unix) |
Beat Bolli <address@hidden> writes:
> On 31.10.13 23:16, Greg Troxel wrote:
>>
>> Beat Bolli <address@hidden> writes:
>>
>>> I have problems connecting to maia.usno.navy.mil, and setting a socket
>>> timeout at least doesn't block the build process.
>>
>> ?
>>
>> It's a bug if the build tries to fetch anything by default.
>
> The fetch is conditional:
>
> if 'dev' in gpsd_version or not os.path.exists('leapseconds.cache'):
>
> You think the first term should be removed?
If it only happens when building from git, that seems ok. I was
reacting to the notion that this could happen to a user building from a
release tarball (both because builds shouldn't fetch, and because the
build might happen on a non-internet-connected machine).
Is the release procedure documented? <esrbait>Back in the good old days
of autotools, I knew how to configure and make distcheck, but now I have
no idea how to prepare a release tarball from git.</>
pgp9p9hvYlP1c.pgp
Description: PGP signature