`stack install --compiler-specific #2643
Comments
I think it would be good to implement this before the next release. My current thoughts on this feature are:
At first I thought it would make sense to put these within the However, this doesn't properly handle the case of having a tool associated with a globally installed ghc. A few options come to mind:
I'm leaning towards doing the 3rd option. What do folks think? |
Caveat: I have only read this issue, so might miss info from #1796.
In other words: compiler-specific tools can't be accessible on the default PATH. Failing that, they shouldn't be accessible via
|
Also, pinging @chrisdone regarding |
These tools would always be available on the PATH when used with a configuration that includes that particular compiler. I'm not thinking very hard about the specifics of intero, because this is a very general feature.
Yeah, it may be reasonable to have a whole new directory structure for this stuff. like |
Is this blocked by anything in particular? I ask because I'd be willing to help if I'm able, if there's tasks that need to be done. I see the PR and it seemed to work based on a very minimal test. I really like this idea, the lack of something-like-this is a lot of why I stopped bothering with fancy things like ghc-mod way back when I switched to stack, and it seems like such a nice clean way to fix. |
@kadoban I wasn't 100% certain it'd solve things nicely for intero, see https://github.com/commercialhaskell/intero/issues/324 . Looking back at it, this seems like a pretty good step in the direction of improving how intero works, and would be helpful for other tools. So I think this just needs to be rebased. Probably lots of conflicts. If you're up to it, would be appreciated! |
Got merged, so closing |
I am splitting this issue off from #1796, because the discussion there got long and so potentially also intimidating. I think this is a very important feature that will be great for
intero
and similar tools. The idea is simple:stack install --compiler-specific
will be a magical incantation that installs tools directly to the compiler bin directory. It is easy to implement, and an important enhancement, so I am marking this P1.For global installs of GHC, it should warn that it might not have the intended semantics. Like if
ghc
is in/usr/local/bin
, we may well be overwritingintero
compiled against a differentghc
, and that might not be expected.The text was updated successfully, but these errors were encountered: