-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add support for cabal-version field values in the form ">= 1.10" #37
Comments
Hi. You're right,
This is on Before we look at solutions, I haven't entirely understand why this constraint is causing a problem. Could you elaborate as to why you need |
I think the problem is that old Cabal spec versions do strictly require the |
I'm not entirely sure it's in the remit of |
PS C:\dhall\dhall-to-cabal> cabal --version
cabal-install version 2.2.0.0
compiled using version 2.2.0.1 of the Cabal library
PS C:\dhall\dhall-to-cabal> type .\dhall-to-cabal.cabal | sls "cab
al-version"
cabal-version: 1.10
PS C:\dhall\dhall-to-cabal> cabal check
The following warnings are likely to affect your build negatively:
* With Cabal 1.10 or earlier, the 'cabal-version' field must use range syntax
rather than a simple version number. Use 'cabal-version: >= 1.10'.
Hackage would reject this package. Although it is a warning the last sentence sounds really bad 😉 Moreover, |
Hi, it seems dhall-to-cabal dont support the
>= 1.10
value in the field, only a simple version like2.0
.However cabal files referencing cabal specs below 1.12 must use the form
>= 1.10
. Although packages should update those versions i guess there are many of them using it yet.Not sure about how to implement it in
dhall-to-cabal
andcabal-to-dhall
:cabal-version
to< Left : ./Version.dhall | Right : ./VersionRange.dhall >
specVersionRaw :: Either Version VersionRange
>= 1.10
Thanks!
The text was updated successfully, but these errors were encountered: