On Fri, Feb 8, 2013 at 10:07 AM, JP Moresmau <span dir="ltr">&lt;<a href="mailto:jpmoresmau@gmail.com" target="_blank">jpmoresmau@gmail.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<div dir="ltr">Johan, thanks, that brings me to a point that I wanted to raise. I&#39;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?</div>

</blockquote><div><br></div><div>I think they will be similar enough that you could easily port the code. The new cabal sandboxing will work as follows:</div><div><br></div><div>cabal sandbox --init</div><div>cabal add-source &lt;dir&gt;</div>

<div><br></div><div>and then you use cabal commands like normal (e.g. configure, build, test). No installing necessary.</div><div><br></div><div>I cannot speak for the cabal-dev developers. We do intend to support a superset of the cabal-dev functionality eventually. What we&#39;re missing now is ghci support.</div>

<div><br></div></div>