<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Due to a problem with the template-haskell package and Cabal, you<br>
cannot cabal-install the emgm package with GHC 6.8. However, take<br>
heart! EMGM works very well with GHC 6.8. You merely have to download<br>
the tar.gz package from Hackage yourself, build it, and install it.<br>
</blockquote>
<br></div>
I thought I had seen you mention a workaround for that issue, but<br>
if not, perhaps you might want to add your experience to<br>
<br>
<a href="http://hackage.haskell.org/trac/hackage/ticket/326" target="_blank">http://hackage.haskell.org/trac/hackage/ticket/326</a><br>
Cabal should support Cabal-version-dependent Setup.hs<br>
</blockquote><div><br>I thought I had worked around it, too. Unfortunately, I can only test once I upload it to Hackage. Once I had, I discovered it wasn't fixed, yet. :-/<br><br>It's a problem with cabal-install/Cabal dealing with the lack of version dependencies in template-haskell. Even though I have template-haskell >= 2.2 in my build-depends, cabal-install insists on trying to install 2.3, which of course fails when you're using GHC 6.8.<br>
<br>Perhaps my problem cannot be fixed within the Setup.lhs? Maybe cabal-install/Cabal is resolving dependencies solely based on the .cabal file? I don't know.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There's a sketched hack-around at the end, using Setup.hs only to call to separate Setup-version.hs files, to circumvent Cabal API<br>
instabilities. Not nice, but perhaps better than to bypass Cabal<br>
alltogether? One would also have to pass parameters, and the<br>
Process API has changed in the meantime.., which I why I still<br>
think Cabal itself should simply be able to pick cabal-versioned configuration and setup files, if they exist.<font color="#888888"><br></font></blockquote></div><br>I like the hack in that ticket. Very nice. ;) Though it apparently fails for multiple versions of Cabal. I just checked my system and it produced:<br>
<br>$ ghc-pkg field Cabal version<br>version: 1.6.0.1<br>version: 1.6.0.2<br><br>Sean<br>