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" <jpmoresmau@gmail.com> wrote:
>
> 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 ..\P1 inside P2
> then cabal-dev install
> Everything works fine, and my project compiles, with modules in P2 calling functions from P1.
> Then I add a new function if an exposed module of P1. I rerun the cabal-dev add-source and cabal-dev install commands to tell P2 of the change, as per the cabal-dev documentation. I change a file in P2 to use the new function, the compilation fails.
> If I check into the cabal-dev folder, I see the .hi file for my changed module has not been updated (old date).
> What am I missing?
>
> Thanks
>
> --
> JP Moresmau
> http://jpmoresmau.blogspot.com/
>
> _______________________________________________
> Haskell-Cafe mailing list
> Haskell-Cafe@haskell.org
> http://www.haskell.org/mailman/listinfo/haskell-cafe
>