You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?)
The text was updated successfully, but these errors were encountered:
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
changed the title
Flag for reinstantiating the sandbox
Environment variables don't seem to get used by anvil builds
Apr 11, 2014
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?
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?)The text was updated successfully, but these errors were encountered: