Thanks for tha, Bárður! It's a bit of a pity that I would have to duplicate many libraries aready installed via arch-haskell / pacman with cabal natively (and I agree, needs to be fully-isolated - I'll look into hsenv, thanks!).
I'm curious - I thought the goal of arch-haskell was to ultimately contain all hackage packages. Snap is in hackage - what makes it difficult to get into arch-haskell? I am not trying to complain - just trying to establish the situation. I am very new to the haskell world, but passionate about it beyond belief. I am happy to help where I can. kind regards, Dawid Loubser Op Di, 2013-10-08 om 19:43 +0200 skryf Bardur Arantsson: > On 2013-10-08 11:54, Dawid Loubser wrote: > > Hi all, > > > > I noticed that neither the snap, nor the yesod web frameworks are in the > > arch-haskell repo - is there a specific reason for this? > > > > What would you recommend is the best way to install and use snap? > > (since it has been made clear that cabal is not a package manager, yet > > snap recommends installing it via cabal... :-S ) > > > > Well, it's not *really* a package manager, but it seems to be growing in > that direction... :) > > Anyway, any users of Snap are probably going to be developers, and I > think it's pretty par for the course for developers to install libraries > they're using from Hackage. > > I would recommend using "hsenv" for keeping per-project Cabal > environments. (The new Cabal will have support for similar isolation, > but I don't think it's really been released yet.) > > Regards, > > Bárður > > _______________________________________________ > arch-haskell mailing list > arch-haskell@haskell.org > http://www.haskell.org/mailman/listinfo/arch-haskell
signature.asc
Description: This is a digitally signed message part
_______________________________________________ arch-haskell mailing list arch-haskell@haskell.org http://www.haskell.org/mailman/listinfo/arch-haskell
