<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hmm…is it possible that the <i>packages</i> entries in my <i>stack.yaml </i>file:<div><br></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div><font face="Menlo">flags: {}</font></div></div><div><div><font face="Menlo">packages:</font></div></div><div><div><font face="Menlo">- '.'</font></div></div><div><div><font face="Menlo">- circat/</font></div></div><div><div><font face="Menlo">- hermit/</font></div></div><div><div><font face="Menlo">- hermit/examples/HIW13/second/plugin/</font></div></div><div><div><font face="Menlo">- hermit/optimizations/pretty/hermit-pretty/</font></div></div><div><div><font face="Menlo">- hermit-extras/</font></div></div><div><div><font face="Menlo">- kure/</font></div></div><div><div><font face="Menlo">- lambda-ccc/</font></div></div><div><div><font face="Menlo">- netlist/netlist/</font></div></div><div><div><font face="Menlo">- netlist/netlist-to-verilog/</font></div></div><div><div><font face="Menlo">- netlist/netlist-to-vhdl/</font></div></div><div><div><font face="Menlo">- netlist/verilog/</font></div></div><div><div><font face="Menlo">extra-deps:</font></div></div><div><div><font face="Menlo">- applicative-numbers-0.1.3</font></div></div><div><div><font face="Menlo">- marked-pretty-0.1</font></div></div><div><div><font face="Menlo">- ty-0.1.5</font></div></div><div><div><font face="Menlo">- type-unary-0.2.19</font></div></div><div><div><font face="Menlo">resolver: lts-2.22</font></div></div></blockquote><div><div><br></div><div>are what guided stack down the right path, re: mimicking the effect of my “cabal sandbox —add-source …” commands?</div><div><br></div><div>And that the version constraints in the “lts-2.22” <i>cabal.config</i> just happened to be what I needed for this project?</div><div><br></div><div>-db</div><div><br></div><div><div>On Sep 3, 2015, at 6:25 AM, Michael Snoyman <<a href="mailto:michael@snoyman.com">michael@snoyman.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div>I'm glad it worked, but I don't think it's doing what you think it's doing. stack intentionally ignores cabal sandbox settings and the like so that the tools don't step on each others' toes. I'm not sure what --add-source you were using, but it's very unlikely that stack picked it up.<br><br></div>I am now quite curious what the problem was and how stack ended up just working for this.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 3, 2015 at 3:32 PM, David Banas <span dir="ltr"><<a href="mailto:capn.freako@gmail.com" target="_blank">capn.freako@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Thanks to all, whom replied.<div><br></div><div>I found that a simple “stack install …” worked perfectly, as an alternative to “cabal install ...". Stack seems to have honored all the “cabal …” things I did in setting up my sandbox, including all my “cabal sandbox —add-source …” commands (5 in all). And, of course, it used the back-rev’d version of ghc I configured it (i.e. - stack) for.</div><div><br></div><div>That is SO neat that I can’t understand why it’s not a featured item in the Stack documentation.</div><div>Thanks, Stack crew!</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>-db</div></font></span><div><div class="h5"><br><div><div>On Sep 2, 2015, at 8:59 PM, Michael Snoyman <<a href="mailto:michael@snoyman.com" target="_blank">michael@snoyman.com</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 3, 2015 at 3:37 AM, David Banas <span dir="ltr"><<a href="mailto:capn.freako@gmail.com" target="_blank">capn.freako@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Hi all,<div><br></div><div>How do I direct cabal to use an alternative (i.e. - not my system’s default) version of ghc, which I’ve installed, via stack?</div><div><br></div><div>I tried this:</div><div><br></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div style="margin:0px;font-size:11px;font-family:Menlo">stack exec cabal install ...</div></blockquote><div><br></div><div>but got this:</div><div><div style="margin:0px;font-size:11px;font-family:Menlo"><br></div></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px"><div><div style="margin:0px;font-size:11px;font-family:Menlo">cabal: Use of GHC's environment variable GHC_PACKAGE_PATH is incompatible with</div></div><div><div style="margin:0px;font-size:11px;font-family:Menlo">Cabal. Use the flag --package-db to specify a package database (it can be used</div></div><div><div style="margin:0px;font-size:11px;font-family:Menlo">multiple times).</div></div></blockquote><div><br></div><div>Thanks,</div><div>-db</div><div><br></div></div><br>_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org" target="_blank">Haskell-Cafe@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe</a><br>
<br></blockquote></div><br></div><div class="gmail_extra">We have a flag to working better with cabal, you can try:<br><br></div><div class="gmail_extra"> stack exec --no-ghc-package-path -- cabal install<br><br></div><div class="gmail_extra">I'm under the impression that there are changes planned to cabal (possibly already implemented but not released) that will allow it to function nicely with the GHC_PACKAGE_PATH environment variable, but I'm uncertain if that's true.<br><br></div><div class="gmail_extra">Michael<br></div></div>
</blockquote></div><br></div></div></div></blockquote></div><br></div>
</blockquote></div><br></div></body></html>