Hi Haskell SIG,
Some of you may have noticed that I did some major repackaging
of ghc's libraries recently (finally managed to persuade
ghc-rpm-macros to allow multiple library subpackages).
This has already been in rawhide ghc for some weeks and
I have now backported the changes to F14, but not
yet pushed the build to f14-updates-testing:
http://koji.fedoraproject.org/koji/buildinfo?buildID=216954
I think this is a good thing (though it does mean
that ghc now has a lot of subpackages!)
since it makes it very clear and transparent what
core libraries are being used by what packages,
and it also puts them on the same footing as other
libraries. This particularly makes sense for libraries
like syb and dph that were moved out of ghc for 7.0.
Note also that all binlib package executables in F15
will be dynamically linked, so separating the shared
libs from ghc-libs seems like a good thing. There is
still a ghc-devel compatibility meta-package, that
pulls in all the ghc-*-devel subpackages from ghc
(except the big ghc API library), which can be used
for now when building bin packages. After F13 goes
EOL I would like to drop the ghc-prof and ghc-devel
BR's from packages and list library dependencies from
ghc explicitly. Packages will also need to BR ghc-Cabal-devel.
cabal2spec should also be able to determine Haskell dependencies
by then I hope.
While I haven't heard any screaming or complaints yet, before
going on I wanted to post here and hear any feedback
or comments on the splitting and plans. I hope people appreciate
the new modularity, but if you feel it could be done better
please speak up. :)
Jens