Re: Cabal woes

Hi, Just wanted to note that the initial Simon's post also mentioned the outdated pages on haskell.org. It'd be good not to forget to purge them, maybe inserting links to cabal.readthedocs. -- Best, Artem On Tue, 16 Apr 2019 at 07:27 Mikhail Glushenkov < mikhail.glushen...@gmail.com> wrote: >

Re: Cabal woes

Hi, On Mon, 15 Apr 2019 at 23:56, Simon Peyton Jones via ghc-devs wrote: > > That’s a tremendously helpful summary, thank you Iavor. And Michail’s > summary was also very helpful. > > > > Most of this is doubtless well-known to habitual cabal users, but it might be > useful to explain the

RE: Cabal woes

. Simon From: Iavor Diatchki Sent: 15 April 2019 23:39 To: Simon Peyton Jones Cc: Brandon Allbery ; ghc-devs@haskell.org Subject: Re: Cabal woes Hello, in case it is useful, here is how I think about what's happening with cabal. At present, `cabal-install` supports two different modes of operation

Re: Cabal woes

Hi Brandon, On Mon, 15 Apr 2019 at 23:46, Brandon Allbery wrote: > > Mikhail, the use case not addressed here is people who are used to v1-style > and want to keep using it — and possibly aren't in a great position to rewire > their setup to fit how v2 thinks. Personally, I have situations

Re: Cabal woes

*Brandon > Allbery > *Sent:* 15 April 2019 23:24 > *To:* Oleg Grenrus > *Cc:* ghc-devs@haskell.org Devs > *Subject:* Re: Cabal woes > > > > The facts here are in the original message: Simon has a cabal-install that > claims to be 3.0.0.0, and is treating "ins

Re: Cabal woes

Mikhail, the use case not addressed here is people who are used to v1-style and want to keep using it — and possibly aren't in a great position to rewire their setup to fit how v2 thinks. Personally, I have situations where I use v2 and others where v1 works better. On Mon, Apr 15, 2019 at 6:43

RE: Cabal woes

To: Oleg Grenrus Cc: ghc-devs@haskell.org Devs Subject: Re: Cabal woes The facts here are in the original message: Simon has a cabal-install that claims to be 3.0.0.0, and is treating "install" as "v2-install". So evidently *someone* has released it in some fashion, per

Re: Cabal woes

Hello Simon, On Mon, 15 Apr 2019 at 23:14, Simon Peyton Jones via ghc-devs wrote: > > It is terribly mysterious that “cabal install hspec” doesn’t, well, install > hspec. In the cabal v2-* model [1] installing libraries globally is no longer the recommended mode of operation, which is why you

Re: Cabal woes

> Simon > > > > *From:* Brandon Allbery > *Sent:* 15 April 2019 22:54 > *To:* Simon Peyton Jones > *Cc:* ghc-devs@haskell.org > *Subject:* Re: Cabal woes > > > > I think you wanted v1-install to install a library into the user package > database, since your c

Re: Cabal woes

t surely be a bug that “cabal install –lib hspec” simply >>crashes. >> >> >> >> Simon >> >> >> >> *From:* Brandon Allbery >> *Sent:* 15 April 2019 23:03 >> *To:* Simon Peyton Jones >> *Cc:* ghc-devs@haskell.org >>

Re: Cabal woes

*From:*Brandon Allbery mailto:allber...@gmail.com>> *Sent:* 15 April 2019 23:03 *To:* Simon Peyton Jones mailto:simo...@microsoft.com>> *Cc:* ghc-devs@haskell.org <mailto:ghc-devs@haskell.org> *Subject:* Re: Cabal woes Yes, I think a lot of documentation will need to

Re: Cabal woes

ous that “cabal install hspec” doesn’t, well, >install hspec. >- It must surely be a bug that “cabal install –lib hspec” simply >crashes. > > > > Simon > > > > *From:* Brandon Allbery > *Sent:* 15 April 2019 23:03 > *To:* Simon Peyton Jones

RE: Cabal woes

Sent: 15 April 2019 23:03 To: Simon Peyton Jones Cc: ghc-devs@haskell.org Subject: Re: Cabal woes Yes, I think a lot of documentation will need to be updated because this. You want "cabal v1-install" with cabal 3. On Mon, Apr 15, 2019 at 6:00 PM Simon Peyton Jones mailto:simo...@mic

Re: Cabal woes

gt; *From:* Brandon Allbery > *Sent:* 15 April 2019 22:54 > *To:* Simon Peyton Jones > *Cc:* ghc-devs@haskell.org > *Subject:* Re: Cabal woes > > > > I think you wanted v1-install to install a library into the user package > database, since your cabal is 3.x and

Re: Cabal woes

>   > > *From:*Brandon Allbery > *Sent:* 15 April 2019 22:54 > *To:* Simon Peyton Jones > *Cc:* ghc-devs@haskell.org > *Subject:* Re: Cabal woes > >   > > I think you wanted v1-install to install a library into the user > package database, since your cabal is 3.

RE: Cabal woes

From: Brandon Allbery Sent: 15 April 2019 22:54 To: Simon Peyton Jones Cc: ghc-devs@haskell.org Subject: Re: Cabal woes I think you wanted v1-install to install a library into the user package database, since your cabal is 3.x and the v2-* commands are now the default (that is, you did what used

Cabal woes

I'm trying to install 'hspec' on my WSL (Windows subsystem for Linux) system. But I fail; see below. For some reason cabal complains about installing a library. (That seems peculiar - isn't that what cabal is for?) But it helpfully suggests adding -lib. Alas, cabal then crashes outright, which