[Haskell-cafe] Re: Library Process (was Building "production
stable" software in Haskell)
johan.tibell at gmail.com
Wed Sep 19 05:05:05 EDT 2007
Building Debian packages seems a bit hard to do for laymen like me.
Anyone have a script that takes a .cabal file, some additional meta
data and creates a .deb package? It would be really nice if we could
make this procedure easier. Every time I read some documentation on
how to create a Debian package, I feel like crying. ;)
On 9/19/07, Simon Marlow <simonmarhaskell at gmail.com> wrote:
> Sven Panne wrote:
> > On Tuesday 18 September 2007 09:44, Dominic Steinitz wrote:
> >> This discussion has sparked a question in my mind:
> >> What is the process for the inclusion of modules / packages in ghc, hugs
> >> and other compilers & interpreters?
> > Personal interest of the people working on GHC et. al. ;-)
> >> I thought the master plan was that less would come with the compiler /
> >> interpreter and the user would install packages using cabal. [...]
> > Although this statement might be a bit heretical on this list, I'll have to
> > repeat myself again that Cabal, cabal-install, cabal-whatever will *never* be
> > the right tool for the end user to install Haskell packages on platforms with
> > their own packaging systems like RPM (the same holds for other systems, I
> > just use RPM as an example here).
> I think you're identifying a non-problem here. Cabal was never intended to
> be used instead of the system's packaging tools for installing packages
> globally on the system, if you look back through the original Cabal design
> discussions you'll see this. We recognised the critical importance of
> working with, rather than around, emerge/ports/RPM/apt/whatever.
> Nowadays from a Cabal package you get make an RPM, a Windows installer, and
> the Gentoo folks have imported the entirety of Hackage. This is how it's
> meant to work.
> Haskell-Cafe mailing list
> Haskell-Cafe at haskell.org
More information about the Haskell-Cafe