Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recommend installing stack instead of MinGHC #75 #87

Merged
merged 4 commits into from
Sep 16, 2015
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 22 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,31 @@
# stack
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right at the head of MinGHC seems a bit surprising. Perhaps this could be a subsection instead?


For most use cases, we recommend [you download and use
stack](https://github.com/commercialhaskell/stack/wiki/Downloads#windows)
instead of proceeding with MinGHC. The MinGHC approach to installing both GHC
and MSYS has been adopted by stack, and stack provides some additional
benefits:

* Easier to upgrade to newer GHC versions
* Support for working with multiple GHC versions without switching environments
* Simple upgrade procedure for stack itself
* Less PATH variable contamination

For more information on using stack, please [read the stack
guide](https://github.com/commercialhaskell/stack/blob/master/GUIDE.md).

MinGHC is still a supported and active project, and makes sense for people
looking for network-free installers for a Haskell toolchain. For more
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or specific GHC versions including older versions.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't you tell stack to use specific GHC versions too?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only back to 7.8

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But we're not uploading anything prior to that anyway?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have 7.2.2 on the web page.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not make an explicit exception in this list saying "if you need an older version of GHC, use MinGHC."

information, see [issue #75](https://github.com/fpco/minghc/issues/75).

# Minimum GHC Installer [![Build Status](https://img.shields.io/travis/fpco/minghc.svg?style=flat)](https://travis-ci.org/fpco/minghc)

This project provides a Windows installer with:

* [GHC](https://www.haskell.org/ghc/), so you can write Haskell code.
* [Cabal](https://www.haskell.org/cabal/), so you can install Haskell packages.
* [stack](https://github.com/commercialhaskell/stack#readme), a modern build tool for Haskell.
* [MSYS](http://www.mingw.org/wiki/MSYS), so packages with configure scripts (notably [network](https://hackage.haskell.org/package/network)) compile.
* [Cabal](https://www.haskell.org/cabal/), an older but still commonly used Haskell build tool.

It _does not_ provide all the packages included with the [Haskell Platform](https://www.haskell.org/platform/), but it _does_ provide an environment where you can install those packages. Some require [installing c libraries](docs/InstallingCLibs.md).

Expand Down