This project is mirrored from https://github.com/haskell/Cabal.
Pull mirroring updated .
- 30 Aug, 2013 4 commits
-
-
Mikhail Glushenkov authored
Fixes #1450.
-
Mikhail Glushenkov authored
-
Mikhail Glushenkov authored
-
Mikhail Glushenkov authored
See #1447.
-
- 23 Aug, 2013 2 commits
-
-
Mikhail Glushenkov authored
Changes back the types of 'configCompiler' and 'configCompilerEx', but marks them as deprecated. Adds new functions 'configCompilerEx' and 'configCompilerAuxEx'. The remaining functions that changed type after the cross-compilation changes shouldn't matter from the backwards compatibility standpoint: * InstallDirs.{absoluteInstallDirs, prefixRelativeInstallDirs, initialPathTemplateEnv} - the versions in D.S.LocalBuildInfo retain their old types and are usually used instead. In any case, removing the Platform parameter from here is problematic because the default install dirs now include $arch and $os vars. * D.S.Configure.configure - shouldn't be used by the setup scripts. See #1214 for the original (backwards-incompatible) patches.
-
Mikhail Glushenkov authored
Helps to disambiguate Cabal's compat modules from cabal-install's.
-
- 27 Jul, 2013 1 commit
-
-
Mikhail Glushenkov authored
Instead, just append '/path/to/.cabal-sandbox/packages' at the end. See the discussion in #1402.
-
- 24 Jul, 2013 1 commit
-
-
Mikhail Glushenkov authored
See #1362.
-
- 10 Jun, 2013 1 commit
-
-
Mikhail Glushenkov authored
-
- 09 Jun, 2013 1 commit
-
-
jhenahan authored
Distribution/Client/Sandbox.hs:695:9: parse error on input `}'
-
- 08 Jun, 2013 1 commit
-
-
Mikhail Glushenkov authored
Also add 'configProgramArgs' and 'configProgramPaths' to the set of special-cased flags.
-
- 07 Jun, 2013 1 commit
-
-
Mikhail Glushenkov authored
Fixes #1360.
-
- 05 Jun, 2013 1 commit
-
-
hesselink authored
-
- 04 Jun, 2013 2 commits
-
-
Mikhail Glushenkov authored
Allows to specify an alternate location for the sandbox config file (@cabal.sandbox.config@) instead of the current directory. Usage: 'cabal --sandbox-config-file=/path/to/config build'. Fixes #1356.
-
Mikhail Glushenkov authored
-
- 03 Jun, 2013 1 commit
-
-
Mikhail Glushenkov authored
-
- 29 May, 2013 1 commit
-
-
Mikhail Glushenkov authored
-
- 17 May, 2013 3 commits
-
-
Mikhail Glushenkov authored
Use the values from 'ConfigFlags' that were read from 'dist/setup-config' instead. This way 'reinstallAddSourceDeps' won't reinstall deps for the wrong compiler, but the user will be forced to use 'install -w' when installing inside a sandbox. This is consistent with the normal mode of operation. Fixes #1333, in a way.
-
Mikhail Glushenkov authored
Fixes #1197. This patch is a bit large because it includes several related changes: 1) Remove 'installUseSandbox' from 'InstallFlags' and pass 'useSandbox' as an additional argument instead. 2) Instead of calling 'reinstallAddSourceDeps' from 'installAction', always pass 'SandboxPackageInfo' to 'install'. 3) Set the timestamps of newly-added add-source deps to 0 in the timestamp file. 4) Move the timestamp file update to 'postInstallActions' from 'withModifiedDeps'. This way, the timestamps are updated even when the user runs 'install --only-dependencies' or 'install some-add-source-dep-package-id'.
-
Mikhail Glushenkov authored
Fixes #1332.
-
- 16 May, 2013 1 commit
-
-
Mikhail Glushenkov authored
Previously, we used a hack for reinstalling reverse dependencies: we created an install plan for the sandboxed package and the modified add-source deps and then pruned the sandboxed package from it. This missed those revdeps that the sandboxed package didn't depend on and also broke the sandboxed package if it was installed in the sandboxed package DB (see #1229). This commit replaces that hack with a more principled approach: we create a plan for the whole environment (all packages installed in the sandbox), constraining the modified add-source deps to be reinstalled and the already installed packages to be preferably not. Fixes #1229.
-
- 15 May, 2013 1 commit
-
-
Mikhail Glushenkov authored
-
- 13 May, 2013 2 commits
-
-
Mikhail Glushenkov authored
Reverts 7b2e3630. Instead of temporarily setting 'configUserInstall' to 'False' in various places, we now just check that we're not in a sandbox when deciding whether we should use 'rootCmd'.
-
Mikhail Glushenkov authored
-
- 09 May, 2013 1 commit
-
-
Mikhail Glushenkov authored
Snapshot deps now behave more like `cabal-dev add-source`. Implemented by adding a BuildTreeRefType field to the BuildRef index entry. Fixes #1321.
-
- 06 May, 2013 1 commit
-
-
Mikhail Glushenkov authored
This avoids the risk of conflicts if we use a single add-source dep with multiple sandboxes.
-
- 05 May, 2013 1 commit
-
-
Mikhail Glushenkov authored
Works better with 'cabal clean'.
-
- 04 May, 2013 1 commit
-
-
Mikhail Glushenkov authored
Fixes #1281.
-
- 03 May, 2013 1 commit
-
-
Mikhail Glushenkov authored
In rare cases, 'cabal.sandbox.config' and 'dist/setup-config' could theoretically become desynchronised. Add a sanity check against this possibility.
-
- 02 May, 2013 3 commits
-
-
Separate listing package sources from copying them over. Allows us to remove a bunch of code from 'D.C.Sandbox.Timestamp'.
-
Mikhail Glushenkov authored
So that we don't reinstall add-source deps for the wrong compiler (e.g. when doing 'cabal build' after 'cabal install -w'). We already do this in configure, and running 'install .' means configuring the current package.
-
Mikhail Glushenkov authored
Fixes #1265.
-
- 30 Apr, 2013 2 commits
- 29 Apr, 2013 5 commits
-
-
refold authored
-
refold authored
-
refold authored
We don't show that command in 'sandbox help' output by default, but if the user is running 'list-sources', she probably wants to know about it.
-
refold authored
Also make it possible to list ignored build tree refs (those present in the index file but not in the source package DB).
-
refold authored
-
- 28 Apr, 2013 1 commit
-
-
refold authored
Unlike 'cabal-dev', we don't create a tarball, but simply copy the files to a private location. Fixes #1143.
-