Hello, I'm trying to understand cabal-dev, and I seem to be missing some
basic point, because I can't get dependencies between projects working
properly.
I have two projects, let's call them P1 and P2. P2 depends on P1, as
indicated by its cabal file build-depends field.
I run cabal-dev add-source
You need to call cabal-dev add-source on P1 again to copy over the sdist,
then do a cabal-dev install.
See notes under Using a sandbox-local Hackage on
https://github.com/creswick/cabal-dev
On Feb 8, 2013 2:22 PM, JP Moresmau jpmores...@gmail.com wrote:
Hello, I'm trying to understand
On Fri, Feb 8, 2013 at 9:53 AM, Blake Rain blake.r...@gmail.com wrote:
You need to call cabal-dev add-source on P1 again to copy over the sdist,
then do a cabal-dev install.
See notes under Using a sandbox-local Hackage on
That's exactly what I'm doing, and I was exactly following these notes, but
it doesn't work. This google+ post and the answers to it (
https://plus.google.com/102016502921512042165/posts/TGaENqWfubP) lead me to
at least one solution that seems to work: you need to unregister the
changed package
Johan, thanks, that brings me to a point that I wanted to raise. I'm
playing with cabal-dev because users have asked me to add support for it in
EclipseFP (so projects could have their own sandbox and have dependencies
between projects without polluting the main package databases). It is worth
it,
On Fri, Feb 8, 2013 at 10:07 AM, JP Moresmau jpmores...@gmail.com wrote:
Johan, thanks, that brings me to a point that I wanted to raise. I'm
playing with cabal-dev because users have asked me to add support for it in
EclipseFP (so projects could have their own sandbox and have dependencies
On Friday, February 8, 2013 at 1:19 PM, Johan Tibell wrote:
On Fri, Feb 8, 2013 at 10:07 AM, JP Moresmau jpmores...@gmail.com
(mailto:jpmores...@gmail.com) wrote:
Johan, thanks, that brings me to a point that I wanted to raise. I'm
playing with cabal-dev because users have asked me to
On Fri, Feb 8, 2013 at 10:24 AM, Ozgun Ataman ozata...@gmail.com wrote:
Which, thanks to Johan's help yesterday, can still be worked around (for
now) by starting ghci with:
ghci -package-conf ./cabal-sandbox/your-package-conf-folder-here/
You can indeed do this. For real ghci support in
