Skip to content
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

Environment variables don't seem to get used by anvil builds #35

Open
rehno-lindeque opened this issue Apr 11, 2014 · 1 comment
Open

Comments

@rehno-lindeque
Copy link
Contributor

When upgrading/adding a lot of dependencies in your .cabal file it will often fail to install unless you add --force-reinstall.

Should we add a flag to run this?

cabal sandbox delete; cabal sandbox init; cabal sandbox install --only-dependencies

It feels a little bit awkward to do all of these sorts of operations via environment variables - would be nice if this was more automatic. I'm not really sure what the best practice is for upgrading cabal dependencies these days, I usually just delete the sandbox and start over when I run into problems...

(Although, perhaps I'm missing something, is this what cabal-constraints is intended for?)

@rehno-lindeque
Copy link
Contributor Author

Actually I think it might just be that that the CLEAR_BUILDPACK_CACHE: 1 flag doesn't seem to work with anvil (i.e. heroku build -r -b https://github.com/begriffs/heroku-buildpack-ghc.git). I forced rebuilding with a branch heroku build -r -b https://github.com/rehno-lindeque/heroku-buildpack-ghc.git#rebuild and that did the trick...

@rehno-lindeque rehno-lindeque changed the title Flag for reinstantiating the sandbox Environment variables don't seem to get used by anvil builds Apr 11, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant