Hello,
what should be the section of the haskell library packages? cabalDebianTemplate[0] uses devel, while haskell-utils[1] uses libdevel.
Why is --enable-library-vanilla in haskell-utils rules[2] CONFIGURE_OPTS if it's in the default cabal options[3]?
Why is --enable-split-objects only used in i386 and amd64? I just got problems with it in s390.
Greetings.
0: http://www.n-heptane.com/nhlab/repos/cabalDebianTemplate 1: /usr/lib/haskell-utils/scripts/current/control.in 2: /usr/lib/haskell-utils/scripts/current/rules 3: http://www.haskell.org/ghc/docs/latest/html/Cabal/builders.html#setup-config...
Hi Marco,
On Fri, Aug 29, 2008 at 06:19:43PM -0300, Marco Túlio Gontijo e Silva wrote:
what should be the section of the haskell library packages? cabalDebianTemplate[0] uses devel, while haskell-utils[1] uses libdevel.
ISTR it's hard to find authoritative descriptions for the sections. http://packages.debian.org/unstable/ says:
devel: Development utilities, compilers, development environments, libraries, etc.
libdevel: Libraries necessary for developers to write programs that use them.
I suspect that the "libraries" in the devel section description is from before the libdevel section was created. I think that libdevel is what we want, anyway.
Why is --enable-library-vanilla in haskell-utils rules[2] CONFIGURE_OPTS if it's in the default cabal options[3]?
Just to be explicit about what's happening.
Why is --enable-split-objects only used in i386 and amd64? I just got problems with it in s390.
Because of problems (or potential problems) with splitting on other arches.
Thanks Ian
On Sat, Aug 30, 2008 at 12:03 AM, Ian Lynagh igloo@earth.li wrote: [...]
Why is --enable-split-objects only used in i386 and amd64? I just got problems with it in s390.
Because of problems (or potential problems) with splitting on other arches.
IIRC there are sometimes problems even on those architectures. Last time I ran into it was when trying to package a vty module from hackage.
/M
debian-haskell@lists.urchin.earth.li