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

Only re-generate cabal file if hpack is new enough #88

Merged
merged 1 commit into from
Apr 2, 2016
Merged

Conversation

sol
Copy link
Owner

@sol sol commented Apr 1, 2016

That is: If a user tries to re-generate an existing cabal file with an
older version of hpack than the one that was used to generate the
existing cabal file, then do nothing.

@sol sol force-pushed the version-check branch 3 times, most recently from c6265d4 to 20108a9 Compare April 1, 2016 10:32
That is: If a user tries to re-generate an existing cabal file with an
older version of `hpack` than the one that was used to generate the
existing cabal file, then do nothing.
@sol sol force-pushed the version-check branch from 20108a9 to 6388008 Compare April 1, 2016 13:51
@sol
Copy link
Owner Author

sol commented Apr 1, 2016

@mgsloan @phadej This might be a more convenient fix for commercialhaskell/stack#1813 / commercialhaskell/stack#1815.

Instead of relying on timestamps, you can just bump the version of your custom version of hpack to e.g. 99.99.99, and upstream hpack will never re-generate your cabal file.

@mgsloan
Copy link
Contributor

mgsloan commented Apr 1, 2016

Seems reasonable, sticking with timestamps for now seems good too until there's some particular issue with that

@sol
Copy link
Owner Author

sol commented Apr 2, 2016

@mgsloan Yes, I agree that we should stick with the timestamps for now.

@sol sol merged commit 6388008 into master Apr 2, 2016
@sol sol deleted the version-check branch April 2, 2016 09:10
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

Successfully merging this pull request may close these issues.

2 participants