-
Notifications
You must be signed in to change notification settings - Fork 843
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
Relax strict Hackage revision matching? #3520
Comments
I like this option + keeping current behavior. Though, it does mean adding a new config option.. eh, seems fine. |
I prefer the |
Looks like this is what I am seeing in commercialhaskell/lts-haskell#74. I am happy that Stack is stricter and builds become more reproducible; the issue is one of documentation. I was not aware of the distinction between |
Alrighty, PR created for the rest of this: I've both added a new flag |
Looks good to me, thanks for the clarification! |
Better errors for 00-index, and ignore-revision-mismatch #3520
I've seen a few different people report the same "not actually a bug" in the Stack prerelease (or from Arch users using a master-based build). The case is:
stack build
et al suddenly stop working with the new Stack releaseThere's a strong argument in favor of keeping this behavior: it provides for proper reproducibility, and usage of 00-index.tar.gz should basically be considered unsupported. On the other hand, revisions are unlikely to break snapshots (though it happens), and therefore we may be able to get away with sweeping this under the rug.
I see a few different options for this next release:
00-index.tar.gz
I'm mostly leaning towards no changes, but wanted to open the discussion.
The text was updated successfully, but these errors were encountered: