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

Update gitignore; cabal.project; aeson-pretty version bounds #65

Merged
merged 1 commit into from
Sep 12, 2019

Conversation

mhuesch
Copy link
Contributor

@mhuesch mhuesch commented Sep 12, 2019

aeson-pretty's Config datatype was updated in 0.8.5 to have a 4th
field. This wasn't captured in the cabal file and I ran into a build
error in a downstream package when an older version of aeson-pretty
was built which lacked the 4th field.

I also add /test to the cabal.project and gitignore the GHC env file.

`aeson-pretty`'s Config datatype was updated in 0.8.5 to have a 4th
field. This wasn't captured in the cabal file and I ran into a build
error in a downstream package when an older version of `aeson-pretty`
was built which lacked the 4th field.

I also add /test to the `cabal.project` and gitignore the GHC env file.
@mhuesch
Copy link
Contributor Author

mhuesch commented Sep 12, 2019

We might also consider adding a CI check to ensure that cabal.project and stack.yaml stay in sync. If people are building with cabal (I am now using it more than stack since it seems to screw up less frequently), it'd be good to support both. We can use cardano-repo-tool to do that.

Copy link
Contributor

@intricate intricate left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@intricate
Copy link
Contributor

intricate commented Sep 12, 2019

We might also consider adding a CI check to ensure that cabal.project and stack.yaml stay in sync. If people are building with cabal (I am now using it more than stack since it seems to screw up less frequently), it'd be good to support both. We can use cardano-repo-tool to do that.

Yup this would be a good idea.

Opened issue: #66

@mhuesch
Copy link
Contributor Author

mhuesch commented Sep 12, 2019

bors r+

iohk-bors bot added a commit that referenced this pull request Sep 12, 2019
65: Update gitignore; cabal.project; aeson-pretty version bounds r=mhuesch a=mhuesch

`aeson-pretty`'s Config datatype was updated in 0.8.5 to have a 4th
field. This wasn't captured in the cabal file and I ran into a build
error in a downstream package when an older version of `aeson-pretty`
was built which lacked the 4th field.

I also add /test to the `cabal.project` and gitignore the GHC env file.

Co-authored-by: Michael Hueschen <[email protected]>
@iohk-bors
Copy link
Contributor

iohk-bors bot commented Sep 12, 2019

@iohk-bors iohk-bors bot merged commit e65b25d into master Sep 12, 2019
@iohk-bors iohk-bors bot deleted the mhuesch/build_tweaks branch September 12, 2019 19:05
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