<div dir="ltr">On Sat, Feb 9, 2013 at 1:34 PM, Carsten Mattner <span dir="ltr"><<a href="mailto:carstenmattner@gmail.com" target="_blank">carstenmattner@gmail.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">
Trying to build and run XMonad from within a cabal sandbox<br>
using the sandbox feature found in cabal HEAD doesn't manage<br>
to build the xmonad binary from xmonad.hs. I belive it's<br>
caused by the ghc calls in XMonad.Core.<br></blockquote><div><br></div><div>xmonad is primarily a library with a stub executable; if you built the library in a sandbox, you have very little choice but to run it in that sandbox. I don't see how this is a bug; it certainly cannot be "fixed", unless you expect xmonad to suddenly learn how to track down *at compile time* that it is being built in a sandbox, and either (a) secretly clone a copy of it somewhere else so it will work even when you tear that sandbox down later, or (b) hardcode a reference to that sandbox into the generated xmonad and hope the sandbox is still there when the user goes to build their xmonad.hs.</div>
<div><br></div><div>(I encourage you to think about the details here.)</div><div><br></div></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div>
<div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</div>