This project is mirrored from Pull mirroring updated .
  1. 20 Jul, 2020 1 commit
  2. 18 May, 2020 1 commit
    • Oleg Grenrus's avatar
      Make cabal-install compilable with NoImplicitPrelude · d4fd273b
      Oleg Grenrus authored
      I.e. find out where we don't yet
      used `Distribution.Client.Compat.Prelude`.
      - If the module is small I added direct `Prelude` imports.
      - Add Exception, deepseq stuff to Cabal Prelude
      - Add Parsec, Pretty and Verbosity to Client Prelude
      - use for, for_, traverse and traverse_ (removes need for Control.Monad)
  3. 06 May, 2020 1 commit
    • Oleg Grenrus's avatar
      Remove sandboxes. · 6248c742
      Oleg Grenrus authored
      Removes command and cleanups cabal-testsuite.
      The tests for #3199 #4099 #3436 are removed, but they seem to be
      sandbox specific issues.
      Removes Sandbox.Types, Sandbox.Index and Sandbox.Timestamp modules.
      The Sandbox and Sandbox.PackageEnvironment are still
      there as some configuration in v1-commands happens through them
      (~/.cabal/config vs ./cabal.config).
      BuildExFlags contained only sandbox specific parameter,
      so it's removed as well.
      Remove sandbox support from cabal-testsuite
      Remove sandbox from GlobalFlags and Sandbox unit-tests
  4. 15 Dec, 2019 1 commit
  5. 07 Mar, 2017 1 commit
  6. 19 Feb, 2017 1 commit
  7. 27 Nov, 2016 1 commit
  8. 22 Nov, 2016 2 commits
  9. 26 Sep, 2016 1 commit
  10. 12 Oct, 2015 1 commit
  11. 11 Oct, 2015 1 commit
    • Adam Gundry's avatar
      Prevent bogus warning in cabal exec · 833da5e2
      Adam Gundry authored
      variables contain colon-separated lists of package DBs, so it doesn't
      make sense to call doesDirectoryExist on the colon-separated list.
      Instead, this just checks for the existence of the sandbox package DB.
  12. 03 Jul, 2015 1 commit
  13. 09 Mar, 2015 1 commit
  14. 06 Mar, 2015 1 commit
  15. 23 Dec, 2014 1 commit
  16. 18 Dec, 2014 2 commits
    • barmston's avatar
      cabal install can be used inside a cabal exec environment · 0a4aed40
      barmston authored
      Inside a cabal exec environment cabal should be configured to always use the
      correct environment. When there is a sandbox this is addressed by setting the
      CABAL_SANDBOX_CONFIG environment variable.
      However GHC is configured to use the correct package database through setting
      the GHC_PACKAGE_PATH environment variable to include the sandbox database. The
      Cabal library previously refused to operate when GHC_PACKAGE_PATH is set in
      order to avoid having a different view of the package databases to GHC.
      In the case of a cabal exec environment being loaded for a cabal sandbox, it
      is safe to allow the use of GHC_PACKAGE_PATH as it is being used to ensure
      that GHC uses the same package database as cabal does.
      A check is made that GHC_PACKAGE_PATH matches the value that cabal exec set it
      to. If it does use of GHC through cabal is permitted.
      Fixes #1800
    • Luite Stegeman's avatar
  17. 29 Jun, 2014 1 commit
  18. 28 Jun, 2014 2 commits