Re: [Haskell-cafe] Cabal failures...
Thanks to all for the comparisons between apt & cabal.
Your reply basically explains why it is broken, and gives a rationale (cost and trouble to do it), but no prognosis for repair.
My interest is in using Haskell for teaching, and so far the package system failures often present problems that I can't solve for all but the simplest examples, so I couldn't much pass this onto students! My libraries may have gotten corrupted, so when I get time I will try to reset and clean out everything and start over, but that will of course break a lot of things and take a lot of time for some re-installs, most particularly things depending on underlying C libraries.
Any hints for a simple way to do this are welcome.
I look forward to the outcomes from the current cabal discussions.
It was also interesting to note a comment that most developers don't have access to a Windows machine for testing. With Windows at >90% of the computing market (Linux = 1.6%), this seems like a problem which might limit growth of Haskell usage. Just an observation. :-)
Thanks for your article on the topic of Cabal - interesting!
----------------------------------------------
Date: Tue, 20 Nov 2012 01:03:20 -0500
From: "Albert Y. C. Lai"
Thanks to all for the comparisons between apt & cabal. Your reply basically explains why it is broken, and gives a rationale (cost and trouble to do it), but no prognosis for repair.
It's an open problem. I make do with disposable sand-boxes, using cabal-dev to build them. In this way, I can keep many (of my) libraries building, even if different libraries need incompatible versions of Hackage libraries. If I run into a problem in a library's build environment, I either fix it surgically or nuke it, without affecting any other build environments.
On 12-11-20 08:48 AM, Gregory Guthrie wrote:
It was also interesting to note a comment that most developers don't have access to a Windows machine for testing. With Windows at >90% of the computing market (Linux = 1.6%), this seems like a problem which might limit growth of Haskell usage. Just an observation. :-)
There is a paradox in that sentence. The first sentence says, most developers don't have access to Windows machines for testing. But they have access to Linux machines. Then Windows machines must be a scarcity compared to Linux machines, no? So scarce, you even have difficulty borrowing or renting. Then the next sentence says, the scarcity is the other way round, Linux machines are scarce, Windows machines are abundant. OK, so why is it so hard to access something abundant, and so easy to access something scarce?
participants (3)
-
Albert Y. C. Lai -
Alexander Solla -
Gregory Guthrie