The recent release of ghc 7.10.2 reminded me of something I meant to
ask about a long time ago. Most of the binaries ghc installs are
versioned (x linked to x-7.10.2), with some exceptions (hpc and
hsc2hs). Shouldn't they all be versioned? Also, 'haddock' is
inconsistent with all the rest, in
On Fri, Jul 31, 2015 at 11:26 AM, Herbert Valerio Riedel
hvrie...@gmail.com wrote:
Btw, I simply prepend to the $PATH env variable, or pass the appropriate
executable name to `cabal`'s
-w --with-compiler=PATHgive the path to a particular compiler
I don't understand, aren't they
On 2015-07-31 at 20:32:43 +0200, Evan Laforge wrote:
On Fri, Jul 31, 2015 at 11:26 AM, Herbert Valerio Riedel
hvrie...@gmail.com wrote:
Btw, I simply prepend to the $PATH env variable, or pass the appropriate
executable name to `cabal`'s
-w --with-compiler=PATHgive the path to
On Fri, Jul 31, 2015 at 2:32 PM, Evan Laforge qdun...@gmail.com wrote:
On Fri, Jul 31, 2015 at 11:26 AM, Herbert Valerio Riedel
hvrie...@gmail.com wrote:
Btw, I simply prepend to the $PATH env variable, or pass the appropriate
executable name to `cabal`'s
-w --with-compiler=PATH
[...] The only thing I find missing is the ability to install a binary
distribution without overwriting the existing symlinks (e.g. ghc -
ghc-7.8.4).
I second the OP's request and Reid's one: I think the binary distributions
for *nices should neither contain unversioned executables nor
On Fri, Jul 31, 2015 at 11:42 AM, Herbert Valerio Riedel
hvrie...@gmail.com wrote:
Sorry, I assumed this w/o saying;
I maintain and use myself
https://github.com/hvr/multi-ghc-travis
Ah, I see. I agree your approach is more principled in that it's local
rather than modifying global state.
Evan Laforge wrote:
The recent release of ghc 7.10.2 reminded me of something I meant to
ask about a long time ago. Most of the binaries ghc installs are
versioned (x linked to x-7.10.2), with some exceptions (hpc and
hsc2hs). Shouldn't they all be versioned? Also, 'haddock' is
Wolfram Kahl wrote:
I use essentially the same setup,
but found that cabal-install does not play nicely with this:
No matter under which prefix I install cabal-install,
it always assumes the same global path for its configuration file.
I install cabal-install from debian which just puts it
On Sat, Aug 01, 2015 at 06:31:38AM +1000, Erik de Castro Lopo wrote:
I maintaing multiple versions of GHC on all the machines I use regularly
for Haskell development. I have:
* ghc-7.6.3 installed under /usr/lib/ghc-7.6/
* ghc-7.8.4 installed under /usr/lib/ghc-7.8/
* ghc-7.10.2 installed