On 13 September 2010 20:54, Paolo Giarrusso p.giarru...@gmail.com wrote:
On Sun, Sep 12, 2010 at 20:46, Tillmann Rendel
ren...@mathematik.uni-marburg.de wrote:
Paolo Giarrusso wrote:
in a tracker entry you linked to,
http://hackage.haskell.org/trac/hackage/ticket/704, duncan argues that
we
Hi Duncan,
first, thanks for coming yourself to answer.
On Wed, Sep 15, 2010 at 18:33, Duncan Coutts
duncan.cou...@googlemail.com wrote:
On 13 September 2010 20:54, Paolo Giarrusso p.giarru...@gmail.com wrote:
On Sun, Sep 12, 2010 at 20:46, Tillmann Rendel
ren...@mathematik.uni-marburg.de
On Sat, Sep 11, 2010 at 12:17:27PM -0700, Jason Dagit wrote:
From the FAQ linked by Paolo:
http://www.haskell.org/cabal/FAQ.html#dependencies-conflict
To avoid this problem in the future, avoid upgrading core packages.
The latest version of cabal-install has disabled the upgrade command
On Sun, Sep 12, 2010 at 20:46, Tillmann Rendel
ren...@mathematik.uni-marburg.de wrote:
Paolo Giarrusso wrote:
in a tracker entry you linked to,
http://hackage.haskell.org/trac/hackage/ticket/704, duncan argues that
we also want to be able to do things like linking multiple versions
of a
Hi Paolo,
Paolo Giarrusso wrote:
- when recompiling a package with ABI changes, does cabal always
update dependent packages?
It never recompiles them. Recompilation should not be needed, because
different versions of packages exports different symbols, so a package
can never be linked
Hi Paolo,
Paolo Giarrusso wrote:
$ cabal install --dry cabal-install leksah-0.8.0.6
[... does not work ...]
However, trying to install cabal-install and leksah separately works quite well.
So do install them separately.
cabal install p1 p2 is supposed to find a single consistent install
On Sun, Sep 12, 2010 at 15:30, Tillmann Rendel
ren...@mathematik.uni-marburg.de wrote:
Paolo Giarrusso wrote:
$ cabal install --dry cabal-install leksah-0.8.0.6
[... does not work ...]
However, trying to install cabal-install and leksah separately works quite
well.
So do install them
Hi!
First, sorry for some confusion - I wanted to post further details
needed for the analysis in the mail I lost, and I had excluded them
from my summary to keep it short.
On Sun, Sep 12, 2010 at 15:26, Tillmann Rendel
ren...@mathematik.uni-marburg.de wrote:
Hi Paolo,
Paolo Giarrusso wrote:
Hi Paolo,
Paolo Giarrusso wrote:
cabal install p1 p2 is supposed to find a single consistent install plan for
p1 and p2 and the transitive dependencies of either of them. This is useful
if you plan to use p1 and p2 in a single project.
Ahah! Then it's a feature. The need for consistency stems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/11/10 15:43 , Daniel Fischer wrote:
On Saturday 11 September 2010 20:38:21, Paolo Giarrusso wrote:
- is there a specification of which are the core packages?
core as in *do not update*?
Basically, what comes with GHC shouldn't be updated.
- when recompiling a package with ABI changes, does cabal always
update dependent packages?
If Foo depends on Bar and there is a new version of Foo that specifies
a newer version of Bar then yes, the newer library being depended on
will be build too (out of necessity).
OTOH, if you are
On Sat, Sep 11, 2010 at 11:56 AM, Thomas DuBuisson
thomas.dubuis...@gmail.com wrote:
- is there a specification of which are the core packages?
Are there packages on which the community standardizes? That's the
goal of Haskell-Platform [1], but I don't place any special value in a
package
On Saturday 11 September 2010 20:38:21, Paolo Giarrusso wrote:
Hi,
after Andrew Coppin's odissey [1], I also had a few problem with
cabal, which stopped installing new packages. Details will follow;
meanwhile, here are some questions prompted by what happened:
- when recompiling a package
On Sat, Sep 11, 2010 at 21:43, Daniel Fischer daniel.is.fisc...@web.de wrote:
On Saturday 11 September 2010 20:38:21, Paolo Giarrusso wrote:
Hi,
after Andrew Coppin's odissey [1], I also had a few problem with
cabal, which stopped installing new packages. Details will follow;
meanwhile, here
Hi all,
sadly, I can't post all details.
I just got a kernel panic and only parts of the detailed log were
saved - my bad (but this is something that kind-of never happens,
except, by Murphy's law, now). I could try reproducing it another
time, but it took some time, so for now I'll rely on my
On Sat, Sep 11, 2010 at 22:29, Paolo Giarrusso p.giarru...@gmail.com wrote:
On Sat, Sep 11, 2010 at 21:43, Daniel Fischer daniel.is.fisc...@web.de
wrote:
I had a broken dependency which I could see with grep but not
otherwise.
ghc-pkg check?
I tried that, but it didn't notice any
On Sat, Sep 11, 2010 at 21:17, Jason Dagit da...@codersbase.com wrote:
On Sat, Sep 11, 2010 at 11:56 AM, Thomas DuBuisson
thomas.dubuis...@gmail.com wrote:
- is there a specification of which are the core packages?
From the FAQ linked by Paolo:
A further pitfall I just discovered:
$ cabal install --dry cabal-install leksah-0.8.0.6
Resolving dependencies...
cabal: cannot configure cabal-install-0.8.2. It requires Cabal ==1.8.*
For the dependency on Cabal ==1.8.* there are these packages: Cabal-1.8.0.2,
Cabal-1.8.0.4 and Cabal-1.8.0.6.
On 9/11/10 3:43 PM, Daniel Fischer wrote:
- is there a specification of which are the core packages?
core as in *do not update*?
Basically, what comes with GHC shouldn't be updated.
Though I heard updating Cabal was okay.
I tried updating Cabal once (recently) and it broke things in the same
19 matches
Mail list logo
