On Sun, Feb 5, 2012 at 12:43 AM, Andres Löh <span dir="ltr"><<a href="mailto:andres.loeh@googlemail.com">andres.loeh@googlemail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Conal.<br>
<div class="im"><br>
> Thanks for the reply! Note that I get this message even running 'cabal<br>
> install' a second time after changing nothing. Is that scenario an example<br>
> of what you mean by a "potentially dangerous cabal invocation"?<br>
<br>
</div>The check currently is entirely ad-hoc. Any reinstallation of an<br>
existing package triggers the warning. There's no hash comparison.<br></blockquote><div><br>I'm confused. Isn't package re-installation an extremely common thing in cabal while developing software? Do you cope by habitually adding --force-reinstall during development? Perhaps that habit is the piece missing from my mental picture.<br>
<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="im">> I've been<br>
> unable to avoid this error message by any other means that (a) 'ghc-pkg<br>
> unregister <package>' or (b) '--force-reinstall'. So far, '--solver=modular'<br>
> hasn't helped. So I'm hoping for something less aggressive. In particular,<br>
> in case nothing has changed, I want 'cabal install' to succeed (exit code 0)<br>
> so that my automated build & install & release processes will continue<br>
> rather than get stopped.<br>
<br>
</div>The message appears, but building should work, with --force-reinstall<br>
and no --dry-run. Can you confirm that you've tried that?<br>
<br>
Cheers,<br>
Andres<br></blockquote><div><br>Yes, building does work for me with --force-reinstall.<br><br>-- Conal<br></div></div><br>