Daniel Fischer schrieb:
On Wednesday 05 May 2010 15:45:38, Henning Thielemann wrote:
Surprisingly using plain Cabal (runhaskell Setup configure; runhaskell
Setup build; runhaskell Setup install) often works in these cases.
That's not surprising.
runhaskell ./Setup.hs configure
can only go
Henning Thielemann schlepp...@henning-thielemann.de writes:
This makes sense. It would be certainly better if cabal-install would
alert about the found inconsistency instead of trying to fix it. Then
there might an additional cabal-install flag, that makes cabal-install
prefer the output of
Henning Thielemann schlepp...@henning-thielemann.de writes:
I meant it the other way round: Given that package X-a.b.c.d does not
compile due to dependencies that turn out to be too restricted, then I
could relax the dependency version bounds in X.cabal. If I also increase
X's version to
On Wed, 2010-05-05 at 12:13 +1000, Ivan Miljenovic wrote:
On 5 May 2010 12:04, Maciej Piechotka uzytkown...@gmail.com wrote:
1. I downloaded happstack-utile[1]
2. Edited cabal file
3. Installed it successfully linking with parsec 3.1
4. I tried to run cabal install happstack --constraint
Maciej Piechotka uzytkown...@gmail.com writes:
Also, I note that you seem to use the Gentoo Haskell overlay (as
you've made bug reports about it) but you're also building packages by
hand; this can also lead to problems (don't mix your packages kids!).
Possibly but:
- I'd like to have
Maciej Piechotka schrieb:
On Wed, 2010-05-05 at 01:09 +0200, Daniel Fischer wrote:
On Mittwoch 05 Mai 2010 00:55:38, Maciej Piechotka wrote:
I try to configure happstack with parsec 3.1. It seems to fail due to
cabal:
happstack-util.cabal says parsec 3, so --constraint=parsec 3 and the
On Wednesday 05 May 2010 15:45:38, Henning Thielemann wrote:
Maciej Piechotka schrieb:
On Wed, 2010-05-05 at 01:09 +0200, Daniel Fischer wrote:
On Mittwoch 05 Mai 2010 00:55:38, Maciej Piechotka wrote:
I try to configure happstack with parsec 3.1. It seems to fail due
to cabal:
On Wed, 2010-05-05 at 01:09 +0200, Daniel Fischer wrote:
On Mittwoch 05 Mai 2010 00:55:38, Maciej Piechotka wrote:
I try to configure happstack with parsec 3.1. It seems to fail due to
cabal:
happstack-util.cabal says parsec 3, so --constraint=parsec 3 and the
given dependencies are
On Wednesday 05 May 2010 01:45:29, Maciej Piechotka wrote:
I updated local copy, as shown, but cabal wants to rebuild it anyway. My
question was rather why the repo is considered at all when the package
is installed.
Regards
Okay, I didn't quite understand your question, sorry.
So, what's
On Wed, 2010-05-05 at 02:17 +0200, Daniel Fischer wrote:
On Wednesday 05 May 2010 01:45:29, Maciej Piechotka wrote:
I updated local copy, as shown, but cabal wants to rebuild it anyway. My
question was rather why the repo is considered at all when the package
is installed.
Regards
On 5 May 2010 12:04, Maciej Piechotka uzytkown...@gmail.com wrote:
1. I downloaded happstack-utile[1]
2. Edited cabal file
3. Installed it successfully linking with parsec 3.1
4. I tried to run cabal install happstack --constraint 'parsec = 3'
5. It complains that happstack-utile needs to be
11 matches
Mail list logo
