haskell/yesod
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

update hsenv documentation

Browse Source
This commit is contained in:
Greg Weber 2013-01-17 08:10:12 -08:00
parent cef52c30c9
commit 77f74c879d
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@ -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