Artem Pelenitsyn authored 2 years ago and andreas.abel committed 2 years ago

- add cabal-install-solver to the list of main packages in the repo

- turn ways to install cabal-install into a list instead of a sequence of headers

- add GHCup as the preferred option for getting cabal

- add a reference to CONTRIBUTING.md

* Convert chat links in badges

* Remove previous links

* Add link to boostrap subdir

* Replace on with via

To not suggest they are separate rooms

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>

This won't work on github
  **[IRC](ircs://libera.chat/#hackage)**
(they have a protocol whitelist) so we link to the webchat

* move them out of the title
* split the super long line in the source

Mikolaj Konarski authored 3 years ago and Mikolaj Konarski committed 3 years ago

AppVeyor produces many false positives for us and we have Windows
github action tests that replicate (part of?) this coverage.

The travis badge shows "build failure" all the time (travis doesn't
run anymore).

To represent the success of GHA builds, I picked the Artifacts
workflow, as this one covers all three OSs (Linux, macOS, Windows).

This follows GitHub's conventions: https://help.github.com/en/articles/setting-guidelines-for-repository-contributors

[ci skip]

I've so often failed to find that link. Let's just add it to the readme.

I notice imports like

    import qualified Text.PrettyPrint as Disp
          ( Doc, render, char, text )

which seem overly precise to me, when `Disp.` is only used
locally as a module prefix, and there's no other imports sharing
the same module prefix.

Instead, it should suffice to either use

    import qualified Text.PrettyPrint as Disp

or

    import Text.PrettyPrint
          ( Doc, render, char, text )

or in rare cases even

    import Text.PrettyPrint as Disp
          ( Doc, render, char, text )

Hence this relaxes the coding guidelines to allow these simpler forms
to be used.

[skip ci]

I've been failing to find this information a few times already. And I still remember not being able to find it the first time, without searching for quite a while. I hope this adds clarity to installing Cabal without cabal, and those who end up with just an unpacked ghc an no cabal to use.

[ci skip]

[ci skip]

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Mikhail Glushenkov authored 8 years ago and Edward Z. Yang committed 8 years ago

It wasn't clear what "three-year support window for cabal-install"
means re: self-upgrade.

[ci skip]

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

[ci skip]

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

7.2.2 was released on Nov 11 2011, so we don't have to support it in
the 2.0 release.

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

[ci skip]

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

[ci skip]

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

[ci skip]

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>

Signed-off-by: Edward Z. Yang <ezyang@cs.stanford.edu>