AFAIK, the way to do this is putting constraints on the base package.<br><br><div class="gmail_quote">On 5 November 2010 14:59, Reiner Pope <span dir="ltr">&lt;<a href="mailto:reiner.pope@gmail.com">reiner.pope@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi,<br>
<br>
I have a library, hmatrix-static, on Hackage. Version 0.3 (the current<br>
version) compiles with ghc-6.12.<br>
<br>
Let&#39;s say I want to upgrade my library using new features in ghc-7.0,<br>
and then release these upgrades as version 0.4. Is there any way to<br>
state in my cabal file that this new version will no longer compile<br>
under ghc-6.12? The reason I would like to state this is so that a<br>
user with ghc-6.12 can do &#39;cabal install hmatrix-static&#39; (or do a<br>
cabal install of a program depending on hmatrix-static) and see that<br>
cabal will install version 0.3 rather than attempt to install version<br>
0.4 and fail.<br>
<br>
Thanks for your help.<br>
<br>
Reiner<br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Ozgur Akgun<br>