Oops, I guess I misinterpreted "package description". It did sound a little dangerous ;-).<div><br>What you suggested also worked. I'm in good shape now. <br><br></div><div><div><div>Thanks again,<br> -Ryan</div>
<div><br><div class="gmail_quote">On Mon, Jan 31, 2011 at 11:24 AM, Duncan Coutts <span dir="ltr"><<a href="mailto:duncan.coutts@googlemail.com" target="_blank">duncan.coutts@googlemail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div>On Mon, 2011-01-31 at 09:52 -0500, Ryan Newton wrote:<br>
> Victory! Thanks!<br>
><br>
> Well.. mostly victory ;-). I've got it in a state where the .cabal<br>
> file rewriting works if "cabal configure" is called separately from<br>
> "cabal build/install" so that the latter reads the modified<br>
> configuration file.<br>
<br>
</div>Yikes! Don't actually modify the .cabal file on disk. I meant just<br>
modify the data structure that gets passed around.<br>
<div><br>
> As for portability... I'm afraid I don't personally do any<br>
> development on Windows. Presumably the goal is for hackage packages<br>
> to work without requiring Cygwin/make/etc?<br>
<br>
</div>Right.<br>
<font color="#888888"><br>
Duncan<br>
<br>
</font></blockquote></div><br></div></div></div>