From 77f74c879da53a639df0b5a60373e455fc50f50d Mon Sep 17 00:00:00 2001 From: Greg Weber Date: Thu, 17 Jan 2013 08:10:12 -0800 Subject: [PATCH] update hsenv documentation --- README.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 0d220005..5a86017a 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,7 @@ Your application is a cabal package and you use `cabal` to install its dependenc Install conflicts are unfortunately common in Haskell development. If you are not using any sandbox tools, you may discover that some of the other haskell installs on your system are broken. -You can prevent this by using sandbox tools: `cabal-dev` or `virthualenv`, now being renamed to `hsenv`. +You can prevent this by using sandbox tools: `cabal-dev` or `hsenv`. Isolating an entire project with a virtual machine is also a great idea, you just need some tools to help that process. [Vagrant](http://vagrantup.com) is a great tool for that and there is a [Haskell Platform installer](https://bitbucket.org/puffnfresh/vagrant-haskell-heroku) for it. @@ -64,7 +64,8 @@ If you aren't building from an application, remove the `./` and create a new dir ## hsenv -We recommend using [hsenv](http://hackage.haskell.org/package/hsenv) when hacking on Yesod from Linux. This is optional, but prevents your custom build of Yesod from interfering with your currently installed cabal packages. +Previously We recommended using [hsenv](http://hackage.haskell.org/package/hsenv) when hacking on Yesod from Linux. +Unfortunately yesod devel's usage of the GHC API does not play nicely with the latest version, so we can only recommend cabal-dev now. hsenv will not work on Windows and maybe not Mac. Use cabal-dev instead