Update release scripts and documentation

Author: borsboom

.gitlab-ci.yml

@@ -19,8 +19,7 @@ build:
     - stable
   script: &build
     - export PATH=$HOME/.local/bin:$PATH
-    - (cd etc/scripts && stack --install-ghc install --pedantic)
-    - stack-release-script check
+    - stack etc/scripts/release.hs check
 
 manual_build:
   stage: build

doc/maintainers/ghc.md

@@ -0,0 +1,83 @@
+<div class="hidden-warning"><a href="https://docs.haskellstack.org/"><img src="https://rawgit.com/commercialhaskell/stack/master/doc/img/hidden-warning.svg"></a></div>
+
+# Adding a new GHC version
+
+  * Push new tag to our fork:
+
+        git clone [email protected]:commercialhaskell/ghc.git
+        cd ghc
+        git remote add upstream [email protected]:ghc/ghc.git
+        git fetch upstream
+        git push origin ghc-X.Y.Z-release
+
+  * [Publish a new Github release](https://github.com/commercialhaskell/ghc/releases/new)
+    with tag `ghc-X.Y.Z-release` and same name.
+
+  * Download all the relevant GHC bindists from https://www.haskell.org/ghc/download_ghc_X_Y_Z and upload them to the just-created Github release (see
+    [stack-setup-2.yaml](https://github.com/fpco/stackage-content/blob/master/stack/stack-setup-2.yaml)
+    for the ones we used in the last GHC release).
+
+    In the case of macOS, repackage the `.xz` bindist as a `.bz2`, since macOS does
+    not include `xz` by default or provide an easy way to install it.
+
+    The script at `etc/scripts/mirror-ghc-bindists-to-github.sh` will help with
+    this. See the comments within the script.
+
+  * [Edit stack-setup-2.yaml](https://github.com/fpco/stackage-content/edit/master/stack/stack-setup-2.yaml)
+    and add the new bindists, pointing to the Github release version. Be sure to
+    update the `content-length` and `sha1` values.
+
+
+## Building GHC
+
+TODO: look into using https://github.com/bgamari/ghc-utils/blob/master/rel-eng/bin-release.sh, which is the script used to official bindists.
+
+On systems with a small `/tmp`, you should set TMP and TEMP to an alternate
+location.
+
+Setup the system based on [these instructions](https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Linux).  On Ubuntu (`docker run -ti --rm ubuntu:16.04`):
+
+    apt-get update && apt-get install -y ghc alex happy make autoconf g++ git vim xz-utils automake libtool gcc libgmp-dev ncurses-dev libtinfo-dev python3
+
+on Void Linux (`docker run -ti --rm voidlinux/voidlinux bash`):
+
+    xbps-install -S curl gcc make xz ghc autoconf git vim automake gmp-devel ncurses-devel python3 cabal-install && \
+    cabal update && \
+    cabal install alex happy
+
+For GHC >= 7.10.2, set the `GHC_VERSION` environment variable to the version to build:
+
+  * `export GHC_VERSION=8.2.2`
+  * `export GHC_VERSION=8.2.1`
+  * `export GHC_VERSION=8.0.2`
+  * `export GHC_VERSION=8.0.1`
+  * `export GHC_VERSION=7.10.3a`
+  * `export GHC_VERSION=7.10.2`
+
+then, run (from [here](https://ghc.haskell.org/trac/ghc/wiki/Newcomers)):
+
+    git config --global url."git://github.com/ghc/packages-".insteadOf git://github.com/ghc/packages/ && \
+    git clone -b ghc-${GHC_VERSION}-release --recursive git://github.com/ghc/ghc ghc-${GHC_VERSION} && \
+    cd ghc-${GHC_VERSION}/ && \
+    cp mk/build.mk.sample mk/build.mk && \
+    sed -i 's/^#BuildFlavour *= *perf$/BuildFlavour = perf/' mk/build.mk && \
+    ./boot && \
+    ./configure --enable-tarballs-autodownload && \
+    sed -i 's/^TAR_COMP *= *bzip2$/TAR_COMP = xz/' mk/config.mk && \
+    make -j$(cat /proc/cpuinfo|grep processor|wc -l) && \
+    make binary-dist
+
+GHC 7.8.4 is slightly different:
+
+    export GHC_VERSION=7.8.4 && \
+    git config --global url."git://github.com/ghc/packages-".insteadOf git://github.com/ghc/packages/ && \
+    git clone -b ghc-${GHC_VERSION}-release --recursive git://github.com/ghc/ghc ghc-${GHC_VERSION} && \
+    cd ghc-${GHC_VERSION}/ && \
+    ./sync-all --extra --nofib -r git://git.haskell.org get -b ghc-7.8 && \
+    cp mk/build.mk.sample mk/build.mk && \
+    sed -i 's/^#BuildFlavour *= *perf$/BuildFlavour = perf/' mk/build.mk && \
+    perl boot && \
+    ./configure && \
+    sed -i 's/^TAR_COMP *= *bzip2$/TAR_COMP = xz/' mk/config.mk && \
+    make -j$(cat /proc/cpuinfo|grep processor|wc -l) && \
+    make binary-dist

doc/maintainers/msys.md

@@ -0,0 +1,31 @@
+<div class="hidden-warning"><a href="https://docs.haskellstack.org/"><img src="https://rawgit.com/commercialhaskell/stack/master/doc/img/hidden-warning.svg"></a></div>
+
+# Upgrading msys
+
+When installing GHC on Windows, Stack will also install
+[msys2](http://www.msys2.org/) to provide a Unix shell and environment,
+necessary for such things as running configure scripts. This section explains
+the steps required to upgrade the msys2 version used by Stack.
+
+1.  Download latest installers from msys2's website. These installers are
+    executables, versioned by date (YYYYMMDD), and are separate for `x86_64`
+    and `i686`. You'll usually be upgrading both at the same time, which we'll
+    assume here.
+
+2.  Run the installer and install to the default location (`c:\msys64` and
+    `c:\msys32`, respectively).
+
+3.  Create tarballs for each directory:
+
+    ```
+    $ cd /c/
+    $ tar cJf msys2-YYYYMMDD-x86_64.tar.xz msys64
+    $ tar cJf msys2-YYYYMMDD-i686.tar.xz msys32
+    ```
+
+4.  Create a new release named `msys2-YYYYMMDD` on the
+    [fpco/stackage-content](https://github.com/fpco/stackage-content)
+    repo, and upload these two files.
+
+5.  Create a PR for the [stack-setup-2.yaml file](https://github.com/fpco/stackage-content/blob/master/stack/stack-setup-2.yaml)
+    to switch over to using the newly uploaded files. You should test this file locally first.