This project is mirrored from https://github.com/haskell/Cabal.
Pull mirroring updated .
- Sep 12, 2022
-
-
Kobayashi authored
* pass some haddock flags to dependencies * add tests * add changelog * fix whitespace * fix test on MacOS
-
- Apr 04, 2020
-
-
Oleg Grenrus authored
- We had to add gpdScannedVersion to permit solver to report about too new packages in the index. https://github.com/haskell/cabal/issues/6652 - It's hard to track what happening with Setup interface selection in ProjectPlanning. https://github.com/haskell/cabal/issues/6651 would help to make sense of it.
-
- Nov 03, 2019
-
-
Edward Z. Yang authored
* Restructure Includes3 tests so that I can also test Hackage case. Signed-off-by:
Edward Z. Yang <ezyang@mit.edu> * Compute correct install directories for instantiated Backpack components Previously, we would compute elabInstallDirs once when configuring a component, and then reuse the exactly same install directories for every instantiation of the package. But this is wrong, since we're installing the header/object files for each instantiation to a different directory. We refactor install directory computation into a helper function and then call it again at instantiation time to refresh the install directories. For some reason, this bug ONLY manifests for packages installed from Hackage; it seems install dirs are not respected for inplace packages. Fixes #6005 Signed-off-by:
Edward Z. Yang <ezyang@mit.edu> * Test fix Signed-off-by:
Edward Z. Yang <ezyang@mit.edu> * Copy backpack version-guard from other backpack testcases
-
- Feb 19, 2017
-
-
Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
-
- Oct 31, 2016
-
-
The key idea is that once we put PackageTests in its own package, we can ensure that its Setup.hs is compiled with the same version of Cabal library as package-tests is compiled with. This means that LBI reading will *always succeed* which is quite nice. Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
-
- Oct 06, 2016
-
-
Edward Z. Yang authored
Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
-
- Feb 15, 2016
-
-
Edward Z. Yang authored
Added tests for this case, as well as some more. This probably breaks the Windows build. Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
-
- Nov 17, 2015
-
-
martinvlk authored
-
- Oct 14, 2015
-
-
Fixes #2797 Squashed commits: - Use ., not source
-
- Oct 23, 2014
-
-
Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
-
- Jul 16, 2014
-
-
Edward Z. Yang authored
Re-exported modules allow packages to reexport modules from their dependencies without having to create stub files. Reexports of the same original module don't count as ambiguous imports when module finding occurs. The syntax is: "orig-pkg" OrigName as NewName You can omit 'as NewName', in which case it is reexported as the same name. Self referential aliases work too; however, they're only visible to packages which depend on this package. Left to future work: just provide a module name 'OrigName', where ghc-pkg figures out what the source package is. Signed-off-by:
Edward Z. Yang <ezyang@cs.stanford.edu>
-