Repository navigation
Not working under hsenv #12
Description
I'm testing out hsenv to manage my packages; I created a new hsenv and installed hdevtools under it; however, unless I also manually specify the -package-conf with -g, it doesn't find packages inside the hsenv. I'm 100% sure I'm using the sandboxed hdevtools, so that's not the problem.
Activity
bitc commentedon Feb 15, 2013
I use hsenv and hdevtools works fine with it. Which version of hsenv are you using? The recommended version is this fork: https://github.com/tmhedberg/hsenv
Can you give more details about your setup?
lightquake commentedon Feb 15, 2013
I'm using GHC 7.4.1, hsenv 0.3 (just cloned it from that repo since I was using the old one), hdevtools 0.1.0.5 (installed from hackage), on OS X 10.8. When I run the hsenv's hdevtools with -g -v it does say that it's using the 'default' user package cache, even though I built it from source under my hsenv.
jwiegley commentedon May 15, 2013
This doesn't work for me either, with the latest hdevtools and hsenv in Hackage.
bitc commentedon May 15, 2013
@jwiegley Which operating system?
jwiegley commentedon May 15, 2013
Mac OS X 10.8.3, using GHC 7.4.2
bitc commentedon May 16, 2013
It seems that this an issue only on Mac OS X then, which I don't use so unfortunately I can't help much. If someone else could figure out what's going on that would be great.
jwiegley commentedon May 16, 2013
I've tried setting -g --package-conf=..., but then I get other errors, like the Text type not matching "...explicit package..Text", when the package mentioned as the explicit package is exactly the one I have installed. Haven't been able to progress beyond that point yet, but I'll keep thinking about it. I miss hdevtools!!
bitc commentedon Jul 4, 2013
Ok, I can confirm that this does not work for regular hsenv usage.
I always use hsenv with the
--ghcoption to install an internal GHC version, and with this usage hdevtools works fine inside the hsenv.Advice/patches on how to fix hdevtools for regular hsenv usage are welcome
polux commentedon Jul 16, 2013
/sub
jwiegley commentedon Jul 16, 2013
I can confirm that hsenv with the
--ghcoption is working great for me too.The only flaw in hdevtools that I can see now, compared to just using ghc, is that I cannot type check against modules in a Cabal project that has never been
cabal-install'd. I constantly find myself having downgrade to plainghcto get checking in these situations.neko-kai commentedon Jul 28, 2013
@jwiegley
You mean configured, not installed? I can check configured, non-installed packages just fine with
jwiegley commentedon Jul 28, 2013
For example, I have the following files:
Foo/Bar.hsFoo/Bar/Baz.hsI edit
Bar.hs, then editBaz.hs.hdevtoolsdoes not see the edits toBar.hswhile checkingBaz.hs, while ghc always does.neko-kai commentedon Jul 29, 2013
@jwiegley
Works for me. Can you provide a testcase?
jwiegley commentedon Jul 29, 2013
Hmm.. I'm having difficulty reproducing in a sample test case, actually. I'll keep an eye out for commonalities in the situations where I'm forced to switch back to ghc.