From 3c3655953174e35590b1892579a54e01c596b8d2 Mon Sep 17 00:00:00 2001 From: Michael Snoyman Date: Mon, 7 Sep 2015 12:44:23 +0300 Subject: [PATCH 1/4] Recommend installing stack instead of MinGHC #75 --- README.md | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 353fab8..a970e15 100644 --- a/README.md +++ b/README.md @@ -1,10 +1,31 @@ +# stack + +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 +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). From 4b5a994a17811f01a3320bf1d9866f89738b32ab Mon Sep 17 00:00:00 2001 From: Michael Snoyman Date: Mon, 7 Sep 2015 18:58:13 +0300 Subject: [PATCH 2/4] That better @3noch? #87 --- README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index a970e15..dbb1289 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,6 @@ -# stack +# Minimum GHC Installer [![Build Status](https://img.shields.io/travis/fpco/minghc.svg?style=flat)](https://travis-ci.org/fpco/minghc) + +## stack For most use cases, we recommend [you download and use stack](https://github.com/commercialhaskell/stack/wiki/Downloads#windows) @@ -14,12 +16,12 @@ benefits: For more information on using stack, please [read the stack guide](https://github.com/commercialhaskell/stack/blob/master/GUIDE.md). +## MinGHC + MinGHC is still a supported and active project, and makes sense for people looking for network-free installers for a Haskell toolchain. For more 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. From 50bb3637582030b823d9bd9f469cceda1c2d17c0 Mon Sep 17 00:00:00 2001 From: Elliot Cameron <3noch@users.noreply.github.com> Date: Tue, 8 Sep 2015 16:20:29 -0400 Subject: [PATCH 3/4] Stop, think, and roll: you might want stack instead --- README.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index dbb1289..b0cb913 100644 --- a/README.md +++ b/README.md @@ -1,19 +1,19 @@ # Minimum GHC Installer [![Build Status](https://img.shields.io/travis/fpco/minghc.svg?style=flat)](https://travis-ci.org/fpco/minghc) -## stack +## Wait, are you sure you don't want `stack`? -For most use cases, we recommend [you download and use -stack](https://github.com/commercialhaskell/stack/wiki/Downloads#windows) +For most use cases we actually 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 +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 +* Simple upgrade procedure for `stack` itself +* Isolated environment that avoids contaminating your `PATH` variable -For more information on using stack, please [read the stack +For more information on using `stack`, please [read the `stack` guide](https://github.com/commercialhaskell/stack/blob/master/GUIDE.md). ## MinGHC From d8611befc14969f2f8dcfd6d7a2dbaa76e78fef1 Mon Sep 17 00:00:00 2001 From: Michael Snoyman Date: Sun, 13 Sep 2015 09:30:41 +0300 Subject: [PATCH 4/4] Add comments about stack ghc/stack runghc/stack exec I think this answers @ndmitchell's concerns. @3noch maybe you have ideas on better wording? --- README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/README.md b/README.md index b0cb913..f8951a4 100644 --- a/README.md +++ b/README.md @@ -16,6 +16,13 @@ benefits: For more information on using `stack`, please [read the `stack` guide](https://github.com/commercialhaskell/stack/blob/master/GUIDE.md). +One note: when using stack, you need to make a few changes to how you +call some tools outside of a project: + +* `stack ghc -- ...` to compile files +* `stack runghc -- ...` to interpret files +* `stack exec -- ...` to run arbitrary commands + ## MinGHC MinGHC is still a supported and active project, and makes sense for people