-
Notifications
You must be signed in to change notification settings - Fork 848
A case when stack does not rebuild but I think it should #2339
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
Comments
There may not be any bugs here, as long as it's using the exact same dependencies. Definitely something that should get tested more! Is it not rebuilding when there's definitely a difference in the build? |
Yes, any new changes in |
Is there some hack workaround, that doesn't involve stack clean, such as telling each stack build to use its own package dbs? |
I will try --force-dirty. Also, I may not be using stack properly, as it might require that I increase the version number of the package (e.g. path-io) in its cabal header, so that downstream packages know that the package has changed? |
Bumping cabal version is a sufficient work around for now for me. --force-dirty didn't save much time relative to stack clean. stack might be behaving correctly by assuming that an upstream library did not need to be rebuilt unless its version number changed. Consider closing this issue and documenting that behavior instead. |
I am closing this given the passage of time and because extra-deps are no longer specified using the |
I have a
path-io
specified as a local package withextra-dep
as true in a package calledpath-test
:path-io
has astack.yaml
of its own and when I make changes in that package I first build and test it using that stack.yaml. After that if I come back to thepath-test
package and do a stack build then it does not rebuild. If I do a stack clean in thepath-io
package (i.e. using path-io's stack-yaml) and then do astack build
inpath-test
then it rebuilds fine.I am not sure why the
path-test
setup gets impacted by thepath-io
setup or whether it should.The text was updated successfully, but these errors were encountered: