This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 15 Jul, 2018 1 commit
  2. 14 Jul, 2018 5 commits
    • Duncan Coutts's avatar
      0403b01f
    • Duncan Coutts's avatar
      Try yet again with the windows file lock problem · 6c09d448
      Duncan Coutts authored
      Try the "retry N times on permission errors" strategy.
      6c09d448
    • Duncan Coutts's avatar
      Add tests for the new 'get -s' implementation · 42e52bbb
      Duncan Coutts authored
      It covers all the failure modes, and currently includes one actual
      network test where we fetch a git repo. There is a new testsuite feature
      flag to disable network tests, and we probably want to use that in CI.
      42e52bbb
    • Duncan Coutts's avatar
      Add QC tests for the VCS abstraction · 9bcd5e20
      Duncan Coutts authored
      This is a hopefully rather comprehensive approach: we generate an
      arbitrary description of how to make a repo, and model what content we
      would expect for every tag/commit. Then we can compare with executing
      the description for the real VCS and comparing the actual file content
      for any tag/commit.
      
      This is then the basis for checking for the various VCS drivers that we
      can (construct and) clone and sync repos properly. In particular for
      syncing this gives some confidence that we can sync for any plausible
      cached previous repo state.
      9bcd5e20
    • Duncan Coutts's avatar
      Add a new VCS abstration · c738ddd1
      Duncan Coutts authored
      This is intended for two things:
       * replacing the Brancher abstraction backing the current 'get -s' impl
       * the basis for source repo support in cabal.package files
      
      The latter is a bit more complex as it requires not just fetching a
      fresh repo, but syncing a repo to a specific tag, commit or branch. The
      approach assumes that we keep a cached copy so that most changes are
      cheap and it optimises things by allowing sharing data between multiple
      commits of the same repo, and multiple packages within the same repo.
      
      For example, it will be possible to specify the same repo in the
      cabal.project file for more than one package, and have those packages
      either in separate subdirs of the same commit, or on different
      commits/tags/branches. In the former case we use a single checkout
      while in the latter case we use two checkouts, but share repo data as
      far as possible.
      c738ddd1
  3. 13 Jul, 2018 3 commits
  4. 07 Jul, 2018 1 commit
  5. 25 Jun, 2018 2 commits
  6. 19 Jun, 2018 1 commit
  7. 15 Jun, 2018 2 commits
  8. 12 Jun, 2018 1 commit
  9. 11 Jun, 2018 1 commit
  10. 16 Apr, 2018 1 commit
  11. 27 Mar, 2018 1 commit
  12. 08 Mar, 2018 1 commit
  13. 16 Feb, 2018 1 commit
  14. 14 Feb, 2018 2 commits
  15. 24 Jan, 2018 1 commit
  16. 21 Jan, 2018 1 commit
  17. 19 Jan, 2018 1 commit
  18. 11 Jan, 2018 1 commit
  19. 05 Jan, 2018 1 commit
  20. 21 Dec, 2017 1 commit
  21. 19 Dec, 2017 2 commits
  22. 02 Dec, 2017 1 commit
  23. 03 Nov, 2017 1 commit
  24. 26 Oct, 2017 3 commits
  25. 22 Oct, 2017 1 commit
    • Moritz Angermann's avatar
      Adds `new-update` · b3af0bab
      Moritz Angermann authored
      new-update uses the new-style logic to update the repositories.  As such it
      respects `repository` fields in the `cabal.project(.local)` file and updates
      them as well.  This is essential when working with hackage overlays, where
      the overlay repositories are specified as `repository` fields in the
      `cabal.project(.local)` file.
      b3af0bab
  26. 14 Oct, 2017 1 commit
    • Francesco Gazzetta's avatar
      Add a new-install command · 9c62e122
      Francesco Gazzetta authored
      Add the first part of the new-install command: nonlocal exes.
      
      See #4558 for the design concept.
      
      This part of the command installs executables from outside of a project
      (ie from hackage) in the store and then symlinks them in the cabal bin
      directory.
      
      This is done by creating a dummy project and adding the targets as extra
      packages.
      9c62e122
  27. 03 Oct, 2017 1 commit
  28. 15 Aug, 2017 1 commit
    • Oleg Grenrus's avatar
      Use parsec, drop parsec flag · 5e4f4d58
      Oleg Grenrus authored
      - Manually generate Lexer.hs
      - Temporarily disable parser-hackage-tests on appveyor (needs
        01-index.tar)
      - Add root Makefile to handle commmon dev tasks (genering Lexer.hs)
      5e4f4d58