Short answer: I had reasons for constraining gtk, etc., to be == 0.11.0.
I will check whether the suggested changes work, and if they do,
include them in the next release of sifflet and sifflet-lib.
Longer answer (quoting parts of 3 different messages):
From: Don Stewart d...@galois.com
So
Don Stewart wrote:
Those specific versions of packages are overly constrained. They should follow
the PVP.
While we're on the subject... Suppose I have a package, which I know
works with foo-8.7.2. What should the Cabal dependents field say? We
have a choice of
foo == 8.7.2
foo = 8.7.2
On Tue, Aug 17, 2010 at 2:54 PM, Andrew Coppin
andrewcop...@btinternet.com wrote:
While we're on the subject... Suppose I have a package, which I know works
with foo-8.7.2. What should the Cabal dependents field say? We have a choice
of
foo == 8.7.2
foo = 8.7.2
foo = 8.7
foo = 8.7
On 18 August 2010 05:04, Anthony Cowley acow...@seas.upenn.edu wrote:
On Tue, Aug 17, 2010 at 2:54 PM, Andrew Coppin
andrewcop...@btinternet.com wrote:
While we're on the subject... Suppose I have a package, which I know works
with foo-8.7.2. What should the Cabal dependents field say? We have
Don Stewart wrote:
So that's pretty simple.
This is one of those 2 3 for sufficiently large 2 things, eh? ;-)
'sifflet' requires cairo ==0.11.0 and pango.
Indeed.
But since
pango doesn't work with cairo 0.11.0, the package can't be built.
Uh... it seemed to build just fine for me
