Skip to content

Loading…

`time` version constraint harmonization #12

Closed
wants to merge 1 commit into from

2 participants

@hvr
Snap Framework member

...otherwise this causes annoying conflicts since time-1.3 has been released and gets picked up by snap-core and snap-server but not by snap

@hvr hvr Remove version constraint from `time` package
As this causes less conflicts with other snap packages whose cabal files
also don't set any version constraints on the `time` package
c5f11e9
@mightybyte
Snap Framework member

Even though in this case the two are equivalent, I prefer to keep the constraints there because it indicates that we've put thought into it. I fixed it without this pull request by widening the bounds.

@mightybyte mightybyte closed this
@hvr
Snap Framework member

Well, could we than add those constraints to all other time dependancies in snap-core and snap-server as well?

@mightybyte
Snap Framework member

Done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Aug 12, 2011
  1. @hvr

    Remove version constraint from `time` package

    hvr committed
    As this causes less conflicts with other snap packages whose cabal files
    also don't set any version constraints on the `time` package
Showing with 1 addition and 1 deletion.
  1. +1 −1 snap.cabal
View
2 snap.cabal
@@ -71,7 +71,7 @@ Library
snap-core >= 0.5.3 && <0.6,
heist >= 0.5 && < 0.6,
template-haskell >= 2.3 && < 2.7,
- time >= 1.0 && < 1.3
+ time
if flag(hint)
build-depends:
Something went wrong with that request. Please try again.