This project is mirrored from https://github.com/haskell/Cabal.
Pull mirroring updated .
- Jan 28, 2016
-
-
Duncan Coutts authored
-
- Jan 27, 2016
-
-
Duncan Coutts authored
Cabal < 1.12.0 doesn't know about '--enable/disable-executable-dynamic' or '--enable/disable-library-coverage'. This is a problem in general, if rare, but it shows up in the nix-local-build branch more obviously since it always passes all flags, including defaults (it does this because the defaults should be determined by the current version, not the older version).
-
Duncan Coutts authored
Make the basic dependencyGraph construction function give us just a Vertex -> UnitId mapping, rather than a full Vertex -> pkg. Then in InstallPlan we keep that Vertex -> UnitId mapping and add a helper function that does the additional lookup to give us a Vertex -> pkg mapping. It's clearer this way, especially in the case of lookup errors.
-
Duncan Coutts authored
This is easier to understand now that the canonical data vs the cached graph is clarified. We only store the main data, the cached info is reconstructed on deserialisation.
-
Duncan Coutts authored
This is to clarify the lazy caching strategy we use for the fields for the Graph (forward and reverse deps, and associated mappings). Reorder the fields, and mark non-lazy fields as strict. Make construction go via a smart constructor that fills in the cached fields.
-
Duncan Coutts authored
Useful for reporting dir/file names in user interface code, e.g. in notices and error messages. Required by later nix-local-build branch patches.
-
Duncan Coutts authored
Required by later nix-local-build branch patches.
-
Duncan Coutts authored
Add Binary instances for many types
-
Duncan Coutts authored
So we can use them in binary cache files. Also relax version constraints on binary to work with binary-0.5.*, which requires that we expose Distribution.Compat.Binary from Cabal. D.Compat.Binary provides the Gerics support that we need to be able to derive instances when using binary-0.5. It's useful to be able to use binary-0.5 since that's the version bundled with older ghc versions.
-
Mikhail Glushenkov authored
remove duplicate LANGUAGE DeriveFoldable, minor improvements
-
Heather authored
-
- Jan 26, 2016
-
-
Mikhail Glushenkov authored
Fix space leak in ./Setup configure
-
Mikhail Glushenkov authored
redundant map after fold
-
Heather authored
-
Mikhail Glushenkov authored
-
Mikhail Glushenkov authored
-
kristenk authored
-
- Jan 25, 2016
-
-
-
Mikhail Glushenkov authored
It uses 'build-type: Simple' now.
-
Mikhail Glushenkov authored
-
Mikhail Glushenkov authored
Fixes #3003.
-
- Jan 24, 2016
-
-
Mikhail Glushenkov authored
Fix bug in solver independent goals.
-
Mikhail Glushenkov authored
Add some more backwards-compatibility functions, fixes #3068.
-
kristenk authored
Missing parentheses caused the solver to skip preferring linked packages with the use of --reorder-goals.
-
- Jan 23, 2016
-
-
Edward Z. Yang authored
Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
-
Mikhail Glushenkov authored
-
- Jan 20, 2016
-
-
Mikhail Glushenkov authored
-
Mikhail Glushenkov authored
-
- Jan 19, 2016
-
-
Mikhail Glushenkov authored
-
Mikhail Glushenkov authored
-
Mikhail Glushenkov authored
Also rename it to '--documentation'. Note that the shorthand still works.
-
- Jan 18, 2016
-
-
Edward Z. Yang authored
Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
-
- Jan 17, 2016
-
-
Mikhail Glushenkov authored
Distinguish between component ID and unit ID.
-
bardur.arantsson authored
Enable tests in setup-dev.sh
-
bardur.arantsson authored
It seems there are no longer any spurious failures, so we can enable tests in setup-dev.sh
-
- Jan 16, 2016
-
-
Edward Z. Yang authored
Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
-
Edward Z. Yang authored
Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
-
Edward Z. Yang authored
Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
-
Edward Z. Yang authored
GHC 8.0 is switching the state sponsored way to specify linker names from -this-package-key to -this-unit-id, so it behooves us to use the right one. But it didn't make much sense to pass ComponentIds to a flag named UnitId, so I went ahead and finished a (planned) refactoring to distinguish ComponentIds from UnitIds. At the moment, there is NO difference between a ComponentId and a UnitId; they are identical. But semantically, a component ID records what sources/flags we chose (giving us enough information to typecheck a package), whereas a unit ID records the component ID as well as how holes were instantiated (giving us enough information to build it.) MOST code in the Cabal library wants unit IDs, but there are a few places (macros and configuration) where we really do want a component ID. Some other refactorings that got caught up in here: - Changed the type of componentCompatPackageKey to String, reflecting the fact that it's not truly a UnitId or ComponentId. - Changed the behavior of CURRENT_PACKAGE_KEY to unconditionally give the compatibility package key, which is actually what you want if you're using it for the template Haskell trick. I also added a CURRENT_COMPONENT_ID macro for the actual component ID, which is something that the Cabal test-suite will find useful. - Added the correct feature test for GHC 8.0 ("Uses unit IDs"). Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
-
Edward Z. Yang authored
Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
-