castle: A tool to manage shared cabal-install sandboxes.
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.
Downloads
- castle-0.1.0.1.tar.gz [browse] (Cabal source package)
- Package description (as included in the package)
Maintainer's Corner
For package maintainers and hackage trustees
Candidates
- No Candidates
Versions [RSS] | 0.1.0.0, 0.1.0.1 |
---|---|
Dependencies | base (>=4.6 && <5), containers, optparse-applicative (>=0.10 && <0.12), shelly, system-fileio, system-filepath, text [details] |
License | Apache-2.0 |
Author | Eric Rochester |
Maintainer | erochest@gmail.com |
Category | Development |
Home page | https://github.com/erochest/castle |
Bug tracker | https://github.com/erochest/castle/issues |
Source repo | this: git clone git://github.com/erochest/castle.git -b master(tag 0.1.0.0) |
Uploaded | by EricRochester at 2015-04-20T17:18:46Z |
Distributions | |
Reverse Dependencies | 1 direct, 0 indirect [details] |
Executables | castle |
Downloads | 1966 total (4 in the last 30 days) |
Rating | (no votes yet) [estimated by Bayesian average] |
Your Rating | |
Status | Docs not available [build log] Last success reported on 2015-12-11 [all 10 reports] |