choener <choe...@tbi.univie.ac.at> writes: > sure, it should be no problem talking about this. I have, however, no > experience with cloud-based computing -- I prefer local clusters, > where we have greater control over what is going on.
I currently use local machinery as well, for practical and political reasons. I do think cloud (that is infrastructure-as-a-service) would be great for a lot of stuff, though. > I regard both my and Ketils libraries as "too unstable" to pre-include > them into a ready-to-use package. "Unstable" here basically means that > we change things too often; though Ketils is already nicely > stable. But if a tool like cabal-dev is available, that is of no big > concern anyway. I do have a bunch of tools that are reasonably stable, and I run weekly tests to ensure that they compile against current hackage. "My" library is a little bit of everything - some stuff is used all over the place, some has little use but extensive testing, some is just experimental. One option - part of the "biocore" effort - could be to factor out the stable and well tested stuff. > An idea for big Haskell installations is to proxy hackage. Almost > everything comes from hackage... but feel free to talk about anything All you need is a network connection, a working, recentish ghc, and a working cabal-install - everything else is then available on-demand. -k -- If I haven't seen further, it is by standing in the footprints of giants _______________________________________________ Biohaskell mailing list Biohaskell@biohaskell.org http://malde.org/cgi-bin/mailman/listinfo/biohaskell
