Fwd: [Fwd: linux version compatible with GHC 4.3 ?]

---------- Forwarded message ---------
From: Damien Mattei

Hello Damien! Here are a couple of points: ---------- Forwarded message ----------
From: Damien Mattei
Subject: linux version compatible with GHC 4.3 ?
Did you mean 8.4.3? All major modern Linux distributions are compatible with this version. But you might run into installation issues, just like with *any other piece of software*.
does anyone know a linux distrib where haskell platform installs out of the box? ...
I see you were able to install GHC on CentOS 7.2, but not on Fedora Core 28. It happens. I can't really tell what might have gone wrong with your installation on Fedora without additional details, such as: what did you actually do for the installation. But it definitely should be possible to install GHC on Fedora.
does it works on Ubuntu?
Yes, I'm using Ubuntu with several different versions of GHC including 8.4.3. I use HVR's ppa for installation: https://launchpad.net/~hvr/+archive/ubuntu/ghc -- Best wishes, Artem

On Mar 18, 2019, at 6:58 PM, Artem Pelenitsyn
wrote: I see you were able to install GHC on CentOS 7.2, but not on Fedora Core 28. It happens. I can't really tell what might have gone wrong with your installation on Fedora without additional details, such as: what did you actually do for the installation. But it definitely should be possible to install GHC on Fedora.
https://github.com/commercialhaskell/stack/issues/1012#issuecomment-23220659... -- Viktor.

Am 19.03.19 um 01:12 schrieb Viktor Dukhovni:
On Mar 18, 2019, at 6:58 PM, Artem Pelenitsyn
wrote: I see you were able to install GHC on CentOS 7.2, but not on Fedora Core 28. It happens. I can't really tell what might have gone wrong with your installation on Fedora without additional details, such as: what did you actually do for the installation. But it definitely should be possible to install GHC on Fedora.
https://github.com/commercialhaskell/stack/issues/1012#issuecomment-23220659...
I switched to installing language tools somewhere in my home directory long ago, because - more frequent breakage than for other types of packages - I want a newer version anyway - common permission issues when installing plugins/libraries My guess about the reasons: - package tools don't have a concept of user-installable extension so many language tools are broken by design (I'm looking at you, Elipse-on-Debian) - the packaged version tends to be older than what you wanted; the faster the language evolves, the more this is a problem - language tools tend to be complicated and fragile, so they have a higher chance of breaking anyway - if there's an issue, the easiest fix for most users is to just install the language tools in the home directory, instead of fixing the package (which often is too slow to solve the immediate problem - this might be different for rolling-release distros, I never tried one of these) Regards, Jo
participants (4)
-
Artem Pelenitsyn
-
Damien Mattei
-
Joachim Durchholz
-
Viktor Dukhovni