This project is mirrored from https://github.com/haskell/Cabal. Pull mirroring updated .
  1. 22 Sep, 2014 5 commits
  2. 20 Sep, 2014 2 commits
  3. 19 Sep, 2014 2 commits
  4. 18 Sep, 2014 3 commits
  5. 17 Sep, 2014 3 commits
  6. 15 Sep, 2014 3 commits
  7. 14 Sep, 2014 7 commits
  8. 13 Sep, 2014 1 commit
    • PeterTrsko's avatar
      Bash completion for "cabal sandbox" subcommands · d00697fa
      PeterTrsko authored
      Command "cabal sandbox --list-options" doesn't list subcommands of
      "cabal sandbox", but "cabal help sandbox" does. It turns out that it is
      easy to parse its output using sed and as such can be added to list of
      words for completion.
      d00697fa
  9. 12 Sep, 2014 1 commit
  10. 10 Sep, 2014 2 commits
  11. 07 Sep, 2014 1 commit
  12. 06 Sep, 2014 3 commits
    • barmston's avatar
      Enable cabal-install tests on travis · 76e52c75
      barmston authored
      76e52c75
    • barmston's avatar
      cabal-install tests use locally built cabal · 3f99cc0c
      barmston authored
      When running the cabal-install tests, we want to run against the locally built
      cabal executable, not any other cabal executable which may be installed.
      
      If we are 1) following the advice of building cabal with `cabal build` (as
      opposed to installing it into a sandbox with `cabal install`) and 2) not using
      a non-default build directory, the locally built cabal will be located at
      `dist/build/cabal/cabal`.
      
      By adding the directory `dist/build/cabal` to the program search path we will
      pick up any cabal executable there in preference to any other on the $PATH.
      
      For most users, I expect that this will remove any surprises with an
      unexpected cabal executable being selected for running the tests. It will be
      sufficient to allow the tests to run on Travis.
      
      For users who have been installing cabal into a sandbox, this change could
      result in an older cabal executable being selected. It's not clear to me how
      to solve this issue or whether anyone will experience this.
      3f99cc0c
    • barmston's avatar
      Exec tests no longer fail if there isn't a sandbox · 4b364b93
      barmston authored
      The tests which delete the sandbox, now check for its existence before
      deleting it. This prevents erroneous test failures when the tests are first
      run or any time that the sandbox has been deleted.
      4b364b93
  13. 30 Aug, 2014 5 commits
  14. 29 Aug, 2014 2 commits