Jacula Modyun writes: [...]
I don't know <(:{?} I'll have to check the haskell port situation, and I'll do it; but, at this moment, I think that, perhaps, it's not worth splitting GHC port. If some software isn't lined up the last version of ghc, it's better, for me, to brand it as broken; there is too much alfa/beta software around the Haskell world and the mark 6.10 is a good boundary.
What he means is to create something equivalent of the current python/ruby ports. Anyone who needs ghc-6.8.x can use ghc-6.8 port and similar for ghc-6.10. But since there are some ports which are having issues with ghc-6.10.x, so keep ghc-6.8.x as default ghc until all ports started to compile with ghc-6.10, and ghc-6.10 for those who are interested in trying out new GHC. -- Ashish SHUKLA