Ah, so you installed the `cabal-install-3.0` package?
Yes I attached your repo and then said
apt install cabal-install
and lo! cabal 3.0 appeared in /opt/cabal/bin
I did this because the vanilla Ubuntu distro only had cabal 1.24. And I could not update by saying “cabal install cabal-install” because cabal 1.24 fell over with that “futex error”.
In the meantime you can just keep using your current cabal 3.0 exe; does `cabal --version` currently have any noticeable startup latency for you on WSL?
No, no noticeable startup latency.
I’ll do the reinstall thing in a few hrs, after you’d done your update. Thanks!
SImon
From: Herbert Valerio Riedel
On Thu, Apr 4, 2019 at 2:56 PM Simon Peyton Jones
Ah, so you installed the `cabal-install-3.0` package?
Yes I attached your repo and then said
apt install cabal-install
and lo! cabal 3.0 appeared in /opt/cabal/bin
Ok, so here's the weird thing... I don't have any "cabal-install" package in my PPA; I do however have a "cabal-install-3.0" package (i.e. the 3.0 is part of the version number, because I supply one package per major version of cabal). So I'd expect you'd find something like ii cabal-install-3.0 3.0+git20190317.1.b3d6d0b-6~16.04 amd64 Command-line interface for Cabal and Hackage if you executed `dpkg -l | grep cabal-install`... (i.e. the "version" is that monstrous "3.0+git20190317.1.b3d6d0b-6~16.04" thing)
In the meantime you can just keep using your current cabal 3.0 exe; does `cabal --version` currently have any noticeable startup latency for you on WSL?
No, no noticeable startup latency.
Interesting. I'll investigate... maybe I'll be able to discontinue the WSL ppa at last... :-)
participants (2)
-
Herbert Valerio Riedel -
Simon Peyton Jones