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, or should I just wait for cabal 1.18 and use the sandboxing facility? Or will the two work similarly enough that supporting both will be easy? Does the sandboxing in cabal means that tools like cabal-dev are going to get deprecated?
Thanks JP On Fri, Feb 8, 2013 at 7:02 PM, Johan Tibell <johan.tib...@gmail.com> wrote: > 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 >> https://github.com/creswick/cabal-de<https://github.com/creswick/cabal-dev> >> > > With the new cabal sandboxing (due in 1.18) this won't be necessary as we > create a link to the repo, instead of installing a copy. We will rebuild > the linked repo as needed. > > -- JP Moresmau http://jpmoresmau.blogspot.com/
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
