
I'll give another recommendation for virthualenv, I've taken to using it
for just about everything I do because it keeps my repo clean. It's
slightly inefficient in that you can end up with many copies of common
libraries, not to mention a full ghc install for every project, but HD
space is cheap, and it saves you time trying to resolve library conflicts
down the line.
On Feb 20, 2012 9:16 AM, "David McBride"
If you want to test something, there are several packages for doing that. cabal-dev and virthualenv both set up repositories in your current directory, allowing you to cabal install packages willy nilly without affecting your global package database. I personally prefer virthualenv (not the spelling), but both are very good programs.
On Mon, Feb 20, 2012 at 2:33 AM, AbdulSattar Mohammed
wrote: I just submitted a patch to Wai, but I didn't like the process I went through while testing it on my machine.
I cloned the repo, modified it and ran
runghc Setup configure --prefix=$HOME --user runghc Setup install
That registered as something like wai-2.1.1.1. ( I don't know what it exactly looked like, but it appended a ".1" to the previous version.) When I ran my test code, it used the latest version. Fine.
But, is this the way everyone does that? I mean, adding a new version? I can't think of any other way, but I'm just against registering the package into the GHC registry. How does everyone do that?
-- Warm Regards,
AbdulSattar Mohammed
_______________________________________________ Beginners mailing list Beginners@haskell.org http://www.haskell.org/mailman/listinfo/beginners
_______________________________________________ Beginners mailing list Beginners@haskell.org http://www.haskell.org/mailman/listinfo/beginners