-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-running installer for helper binaries gives up #274
Comments
Good point! What do you think of having some kind of "force helper binary install" flag or something? By default, users wouldn't have to wait on them if they already have them installed, but if they specify the force flag, they will rebuild regardless of stack.yaml being there. |
Yeah, a force install flag would work. It could also check for the presence of the generated helper binaries rather than for the stack file. |
|
Maybe the presence of the hvn-helper-binaries directory would speed up binary rebuilds? Otherwise we'd have to rebuild all those deps... But maybe rebuilding binaries happens so rarely that it's worth it to clear out that directory after a successful install. I'd take a pull request if you're interested in doing an rmtree on it. |
The logic checks for a
~/.config/haskell-vim-now/hvn-helper-binaries/stack.yml
, and if found considers the binaries to be built and skips further work. However if a previous installation was interrupted then this file will exist and the installer will never make the binaries.https://github.com/begriffs/haskell-vim-now/blob/master/scripts/setup_haskell.hs#L130-L131
The text was updated successfully, but these errors were encountered: