distributed-process-platform
distributed-process-platform copied to clipboard
Fix Travis-CI Install Procedure
Depends on issue #9
We are on travis-ci now, but the build repeatedly fails to install dependencies.
The latest build failure is happening because the latest exit/catchExit changes have not been released by distributed-process, or so it seems.
src/Control/Distributed/Platform/GenServer.hs:52:60:
573 Module `Control.Distributed.Process' does not export `exit'
The latest build failure is happening because the latest exit/catchExit changes have not been released by distributed-process, or so it seems.
Hmn, you're quite right. I think I'll hack the makefile to handle that for the time being. Would be good to hear from @edsko when the next release is likely to be first though. Until it becomes available on hackage, I'll probably git clone the distributed-process repo into a temp folder and cabal install it from there as a pre-build hook. It'll be much better not to do that in future though....
Whether or not we release a new version of CH any time soon should be irrelevant to this discussion. It's not unlikely that distributed-process-platform will continue to depend on features that are (temporarily) available in HEAD only.
Whether or not we release a new version of CH any time soon should be irrelevant to this discussion. It's not unlikely > that distributed-process-platform will continue to depend on features that are (temporarily) available in HEAD only.
Good point. I'll plonk some code into the makefile to handle this.
Also.... It would be nice if travis-ci supported multiple versions of ghc and custom dependencies. We could use virthualenv to achieve this (for multiple ghc versions) or cabal-dev for custom dependencies (but not multiple ghc afaict). I might patch https://github.com/travis-ci/travis-build/blob/master/lib/travis/build/job/test/haskell.rb and send a pull request.