Skip to content

Conversation

@mmhat
Copy link
Contributor

@mmhat mmhat commented Feb 26, 2023

Without that running the tests via Cabal fails with: could not execute: hspec-discover
Moved these changes from #63 to a separate PR as suggest in #63 (comment).

Without that running the tests via Cabal fails with:
could not execute: hspec-discover
Copy link
Contributor

@sol sol left a comment

Choose a reason for hiding this comment

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

  1. hpack does not require you to specify the package name if the package name and executable name coincide
  2. You should use the exact same versions of hspec and hspec-discover. stack ensures this, cabal currently does not really ensure a consistent set of dependencies (haskell/cabal#5105), but in most cases you will get a consistent set by "being lucky". Adding an additional version constraint for hspec-discover will not meaningfully improve anything for cabal and is hence unnecessary clutter.

Comment on lines +39 to +40
build-tools:
- hspec-discover:hspec-discover >=2 && <3
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
build-tools:
- hspec-discover:hspec-discover >=2 && <3
build-tools: hspec-discover

Comment on lines +49 to +50
build-tools:
- hspec-discover:hspec-discover >=2 && <3
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
build-tools:
- hspec-discover:hspec-discover >=2 && <3
build-tools: hspec-discover

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