The castle package
I really like having sandboxes baked into cabal-install.
However, I got tired of waiting for big packages like Yesod and Lens to compile in project after project that used them. However, I still didn't want to install them in the user database. I wanted to maintain some sandboxing among a group of projects that all share a common set of packages, but I wanted to be able to switch from them or upgrade them easily.
That's the itch I was trying to scratch with castle.
It allows you to share one Cabal sandbox between multiple projects. This keeps the package versions for all of these projects in line. It also means that you don't have to constantly be re-installing everything, but you still get the ability to blow away a set of packages without borking your whole system.
|Change log||None available|
|Dependencies||base (>=4.6 && <5), containers, optparse-applicative (>=0.10 && <0.12), shelly, system-fileio, system-filepath, text|
|Source repository||this: git clone git://github.com/erochest/castle.git -b master(tag 0.1.0.0)|
|Uploaded||Mon Apr 20 17:18:46 UTC 2015 by EricRochester|
|Downloads||241 total (21 in last 30 days)|
|Status||Docs not available [build log]|
Last success reported on 2015-05-18 [all 2 reports]
For package maintainers and hackage trustees