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.
- No changelog available
|Dependencies||base (==4.6.*), configurator, containers, errors, lens, optparse-applicative, 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||Wed Jan 15 20:20:02 UTC 2014 by EricRochester|
|Downloads||139 total (8 in last 30 days)|
|Status||Docs not available [build log]|
Successful builds reported [all 1 reports]
For package maintainers and hackage trustees