On Fri, Nov 1, 2013 at 6:30 AM, Gregory Guthrie <guthrie@mum.edu> wrote:
   "I *strongly* suggest everyone start transitioning from cabal-dev to cabal sandboxes."

Is there any reason that this is not just the default install mode for Cabal?

I'm on the fence about this -- iirc, ruby has a similar concept (revn?) that has this default, and it can be quite confusing (and, in my experience, generates a fair bit of clutter, although that would probably go down with experience.)

Perhaps if cabal prompted for confirmation when creating a new sandbox (but only if running in an interactive context)? I could see my self inadvertently cabal-installing utilities (eg: newt, bnfc, etc...) in sandboxes on accident.

--Rogan

 

Anything that prevents the current cabal-swamp of broken dependencies is a great help. I have tried to use Haskell in some classes, but it is hard when students (and I) cannot install packages, and the only answer is the Microsoft-like; "delete everything and start over; reinstall". It certainly reduces their confidence that Haskell is a feasible working environment.

_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe