1. 25 Mar, 2014 2 commits
    • Avoid re-downloading if there's a valid tarball in build location · 1bcd249f
      If there already exists a valid tarball in the build location, e.g. as
      artefact of a previous install using `--keep`, don't re-download the
      file, as there is no need.
      
      References #487
      Mislav Marohnić committed
    • Fix re-downloading tarball when destination file already exists · a3009b46
      Previously, curl and wget were instructed to try to resume the download
      if the destination file already exists. This is supposed to be done via
      the "Range" HTTP header, but doesn't work well with CloudFront:
      
          HTTP server doesn't seem to support byte ranges. Cannot resume.
      
      CloudFront is supposed to support ranges, so I don't know what's going
      on here. It might be failing only in case the existing file is a fully
      downloaded tarball?
      
      In any case, this disables resuming downloads and resorts to simply
      re-downloading the tarball always, overwriting the existing file.
      
      Fixes #487
      Mislav Marohnić committed
  2. 18 Mar, 2014 1 commit
  3. 17 Mar, 2014 1 commit
  4. 12 Mar, 2014 1 commit
  5. 11 Mar, 2014 1 commit
  6. 26 Feb, 2014 7 commits
  7. 25 Feb, 2014 2 commits
  8. 24 Feb, 2014 10 commits
  9. 18 Feb, 2014 2 commits
  10. 17 Feb, 2014 2 commits
  11. 14 Feb, 2014 3 commits
  12. 10 Feb, 2014 7 commits
  13. 09 Feb, 2014 1 commit