Cabal: Nix-style Local Builds documentation is confusing

[brunom]

You shouldn't use Cabal and cabal-install as examples in the cabal documentation. The reader has to mentally quote stuff to understand which level the text is talking about.

[phadej]

It took me a moment to unquote your comment, indeed :) Anu suggestions for example packages?

Sent from my iPhone

On 21 Feb 2018, at 17.03, Bruno Martinez [e-mail] wrote:

You shouldn't use Cabal and cabal-install as examples in the cabal documentation. The reader has to mentally quote stuff to understand which level the text is talking about.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[brunom]

network and http-client

[phadej]

I think we need something with an executable

[peti]

How about stack? :grin:

[ivan-m]

hlint? pandoc?

[neosimsim]

hfmt, haskell-docs?

[linearray]

What about tasty? Its cabal.project has more than one package entry.

[phadej]

I'd prefer a package cabal maintainers have influence. Having cabal.project is good point too. I'm maintainer of servant, but it's not good (for the same reason as tasty) as it's controversial. (i.e. servant vs scotty; tasty vs hspec - maybe I overthink, but I'd avoid "advertising"). OTOH current cabal.project uses constraints and allow-newer, so the examples could be quite real.

Opinions?