On 09/02/2014 05:17 PM, Ben Pfaff wrote:
On Tue, Sep 02, 2014 at 05:15:16PM +0200, Bernhard Voelker wrote:
On 09/02/2014 05:06 PM, Ben Pfaff wrote:
Looking at wget(1), I'm a little surprised that the selected options
appear to avoid clobbering files whose names conflict. I would have
expected
On 09/02/2014 05:06 PM, Ben Pfaff wrote:
Looking at wget(1), I'm a little surprised that the selected options
appear to avoid clobbering files whose names conflict. I would have
expected that we'd want to overwrite them, to get the fresher version.
But the existing wget invocation does the same
On Tue, Sep 02, 2014 at 05:15:16PM +0200, Bernhard Voelker wrote:
> On 09/02/2014 05:06 PM, Ben Pfaff wrote:
> >Looking at wget(1), I'm a little surprised that the selected options
> >appear to avoid clobbering files whose names conflict. I would have
> >expected that we'd want to overwrite them,
On Tue, Sep 02, 2014 at 12:22:54PM +0200, Mathieu Anquetin wrote:
> Current implementation only tries to rsync PO files when rsync is
> installed on the host. In case of error, no files are downloaded even
> if they are available. This leads to bootstrap problems for hosts
> that lie behind a restr
Current implementation only tries to rsync PO files when rsync is
installed on the host. In case of error, no files are downloaded even
if they are available. This leads to bootstrap problems for hosts
that lie behind a restrictive firewall.
This patch always tries to rsync by default, falling bac
