[Haskell-cafe] ANN: castle 0.1.0.0
cma at bitemyapp.com
Thu Jan 16 00:45:38 UTC 2014
I typically do the same, fairly frequently, using a Makefile to handle
configuring builds/cabal/whatever to all point to the same sandbox or
pulling it from my environment variables.
On Wed, Jan 15, 2014 at 4:30 PM, Ivan Lazar Miljenovic <
ivan.miljenovic at gmail.com> wrote:
> On 16 January 2014 07:24, Eric Rochester <erochest at gmail.com> wrote:
> > I'd like to announce the first release of castle
> > (http://hackage.haskell.org/package/castle and
> > https://github.com/erochest/castle). From the README:
> >> I really like having sandboxes baked into cabal-install (see Cabal
> >> Sandboxes for more information).
> >> I got tired of waiting for big packages like Yesod and Lens to compile
> >> 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
> >> that you don't have to constantly be re-installing everything, but you
> >> get the ability to blow away a set of packages without borking your
> >> system.
> > This tool is still pretty rough around the edges, but I've been using it
> > some, and it's to the point that more feedback would be helpful. Let me
> > what bugs and rough patches you find.
> How does this differ from doing "cabal sandbox init
> --sandbox=../my-common-sandbox" for all these projects?
> Ivan Lazar Miljenovic
> Ivan.Miljenovic at gmail.com
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Haskell-Cafe