|Subject:||[Haskell-cafe] Cabal pre-compiled packages|
|Date:||Sat, 27 Feb 2010 11:55:12 -0300|
currently when one install a cabal package it compiles it and then install generated binaries. I wonder whether or not it would be useful to have pre-compiled binaries as many package managers usually do (e.g. apt). I often think that would save some time on the expense of a busier hackage server capable of generating packages for many different platforms.
I'm particularly thinking on the following scenario: suppose that you have code that is ready for production. If cabal supported pre-compiled binaries, there is no need to install ghc or eventually any other compiler, just runtime environment and eventually cabal. I must say that I have no experience in doing this in Haskell (just personal/small projects), so I suppose one have to generate binaries and use other sort of package manager to deploy code to production (which sounds reasonable as well). Thus, if the assumption is correct, cabal is a development tool, not something one could to only deploy runtime-only packages.
I also would appreciate if others could share how usually this is managed.
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@xxxxxxxxxxx http://www.haskell.org/mailman/listinfo/haskell-cafe
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [Haskell-cafe] Testing and module export lists, Ivan Miljenovic|
|Next by Date:||Re: [Haskell-cafe] Cabal pre-compiled packages, Andrew Coppin|
|Previous by Thread:||[Haskell-cafe] How to understand `|` in this code snippet ?, zaxis|
|Next by Thread:||Re: [Haskell-cafe] Cabal pre-compiled packages, Andrew Coppin|
|Indexes:||[Date] [Thread] [Top] [All Lists]|