Merge pull request #1 from fpco/master

merge with fpco
2026-01-12 07:18:31 +01:00 · 2015-10-09 14:29:40 -04:00 · 2015-10-09 14:29:40 -04:00 · aff3e64fa9
commit aff3e64fa9
parent f31e09dc98 8e0e01ec8f
15 changed files with 1406 additions and 188 deletions
--- a/.gitignore
+++ b/.gitignore
@ -2,3 +2,4 @@
 /logs/
 nightly-*.yaml
 lts-*.yaml
+*.swp
--- a/.travis.yml
+++ b/.travis.yml
@ -1,21 +1,27 @@
-env:
- - CABALVER=1.20 GHCVER=7.8.4
+sudo: false

-# Note: the distinction between `before_install` and `install` is not important.
-before_install:
- - travis_retry sudo add-apt-repository -y ppa:hvr/ghc
- - travis_retry sudo apt-get update
- - travis_retry sudo apt-get install cabal-install-$CABALVER ghc-$GHCVER # see note about happy/alex
- - export PATH=/opt/ghc/$GHCVER/bin:/opt/cabal/$CABALVER/bin:$PATH
+language: haskell

 install:
- - cabal --version
- - echo "$(ghc --version) [$(ghc --print-project-git-commit-id 2> /dev/null || echo '?')]"
- - travis_retry cabal update
+ # Get stackage-curator
 - wget https://s3.amazonaws.com/stackage-travis/stackage-curator/stackage-curator.bz2
 - bunzip2 stackage-curator.bz2
 - chmod +x stackage-curator

-# Here starts the actual work to be performed for the package under test; any command which exits with a non-zero exit code causes the build to fail.
+ # Get stack
+ - travis_retry curl -L https://github.com/commercialhaskell/stack/releases/download/v0.1.3.0/stack-0.1.3.0-x86_64-linux-gmp4.gz | gunzip > stack
+ - chmod +x stack
+
+ # Install GHC and cabal-install
+ - ./stack setup 7.10.2
+ - ./stack --resolver ghc-7.10 build stackage-update
+
+ # Update the index
+ - travis_retry ./stack --resolver ghc-7.10 exec stackage-update
+
 script:
- - ./stackage-curator check
+ - ./stack --resolver ghc-7.10 exec ./stackage-curator check
+
+cache:
+  directories:
+    - $HOME/.stack
--- a/CURATORS.md
+++ b/CURATORS.md
@ -0,0 +1,118 @@
+This is a collection of instructions for what Stackage curators- the guys who
+maintain the Stackage project itself- should be doing on a regular basis. At
+the time of writing (July 2015), this is handled almost entirely by Michael
+Snoyman. Curation activities are mostly automated, and do not take up a
+significant amount of time. But it's good to spread the knowledge for obvious
+reasons (errant buses, if I ever decide to take a vacation...).
+
+## Workflow
+
+This section sketches out at a high level how the entire Stackage build/curation
+process works:
+
+* [build-constraints.yaml](https://github.com/fpco/stackage/blob/master/build-constraints.yaml) specifies packages to be included in Stackage
+* [stackage-curator](http://www.stackage.org/package/stackage-curator) combines build-constraints.yaml with the current state of Hackage to create a build plan for a Stackage Nightly
+* stackage-curator can check that build plan to ensure all version bounds are consistent
+    * The [Travis job](https://github.com/fpco/stackage/blob/master/.travis.yml) performs these two steps to provide immediate feedback on pull requests
+* Docker Hub [builds](https://github.com/fpco/stackage/blob/master/Dockerfile) a [Docker image](https://registry.hub.docker.com/u/snoyberg/stackage/) for running builds
+* The stackage-build server (described below) is able to run automated builds using the [build.sh script](https://github.com/fpco/stackage/blob/master/automated/build.sh)
+* When a new Nightly build is completed, it is uploaded to [the nightly repo](https://github.com/fpco/stackage-nightly)
+* Once a week, we run an LTS minor bump. Instead of using build-constraints.yaml, that job takes the previous LTS release, turns it into constraints, and then bumps the version numbers to the latest on Hackage, in accordance with the version bounds in the build plan. This plans are uploaded to [the LTS repo](https://github.com/fpco/lts-haskell)
+* Cutting a new LTS major release is essentially just a Stackage Nightly that gets uploaded as an LTS
+
+## Pull requests
+
+The typical story on pull requests is: if Travis accepts it, and the author
+only added packages under his/her own name, merge it. If the build later fails
+(see below), then block the package until it's fixed.
+
+## Fixing bounds issues
+
+The most common activity you'll deal with in Stackage curation is a version
+bound issue, usually a restrictive upper bound. You fix this by opening an
+issue on the Stackage repo about the problem, and modifying the
+build-constraints.yaml file to work around it in one of the ways below. Be sure
+to refer to the issue for workarounds added to that file.
+
+* __Temporary upper bounds__ Most common technique, just prevent a new version of a library from being included immediately
+* __Skipping tests and benchmarks__ If the upper bound is only in a test suite or benchmark, you can add the relevant package to skipped-tests or skipped-benchmarks. For example, if conduit had an upper bound on criterion for a benchmark, you could added conduit as a skipped benchmark.
+* __Excluding packages__ In an extreme case of a non-responsive maintainer, you can remove the package entirely from Stackage. We try to avoid that whenever possible
+
+## Updating the content of the Docker image used for building
+
+### Adding Debian packages for required system tools or libraries
+Additional (non-Haskell) system libraries or tools should be added to `stackage/debian-bootstrap.sh`.
+Committing the changes should trigger a DockerHub. Normally only the master branch needs to be updated
+since new packages are not added to the current lts release.
+
+Use [Ubuntu Package content search](http://packages.ubuntu.com/) to determine which package provides particular dev files (it defaults to trusty which is the same version as the server).
+
+### Upgrading GHC version
+The Dockerfile contains information on which GHC versions should be used. You
+can modify it and push it to Github to trigger a DockerHub build. The master
+branch is used for nightlies, and the lts branch for LTS.
+
+### Getting the new image to the build server
+Once a new Docker image is available, you'll need to pull it onto the stackage-build server (see
+below). Instead of pulling an unbounded number of images, I typically just
+delete all of the old images and let the new ones get downloaded:
+
+```
+docker rm $(docker ps -a -q)
+docker rmi $(docker images -q)
+```
+
+but `docker pull snoyberg/stackage:nightly` can also be run instead just to update the nightly image say.
+
+For a new GHC version you should also delete the cache directories on the stackage-build server to
+force all packages to be rebuilt. See: [issue#746](https://github.com/fpco/stackage/issues/746).
+
+## stackage-build server
+
+You'll need to get your SSH public key added to the machine. ~/.ssh/config info:
+
+```
+Host stackage-build
+    User ubuntu
+    Hostname ec2-52-5-20-252.compute-1.amazonaws.com
+```
+
+We currently run the builds manually so make it easy to see when there are
+bounds issues that need to be corrected. Automated this would be even better,
+we're just not there yet.
+
+```
+# Run a nightly build
+/opt/stackage-build/stackage/automated/build.sh nightly-2015-07-08
+
+# Run an LTS minor bump
+/opt/stackage-build/stackage/automated/build.sh lts-2.17
+
+# Run an LTS major bump
+/opt/stackage-build/stackage/automated/build.sh lts-3.0
+```
+
+Recommended: run these from inside a `screen` session. If you get version bound
+problems on nightly or LTS major, you need to fix build-constraints.yaml (see
+info above). For an LTS minor bump, you'll typically want to use the
+`CONSTRAINTS` environment variable, e.g.:
+
+```
+CONSTRAINTS='--constraint "conduit < 1.4.5" --constraint "criterion < 1.2.3"' /opt/stackage-build/stackage/automated/build.sh lts-2.17
+```
+
+If a build fails for bounds reasons, see all of the advice above. If the code
+itself doesn't build, or tests fail, open up an issue and then either put in a
+version bound to avoid that version or something else. It's difficult to give
+universal advice on how to solve things, since each situation is unique. Let's
+develop this advice over time. For now: if you're not sure, ask Michael for
+guidance.
+
+### Timing
+A cronjob on the build server keeps trying to build nightly unless it has already succeeded.
+
+(Nightly builds should be run once a day. A common technique I use is, after a
+build succeeds, write something like `sleep 20h;
+/opt/stackage-build/stackage/automated/build.sh nightly-2015-01-02`.)
+
+LTS minor bumps typically are run on Sundays.
--- a/14
+++ b/14
@ -1,4 +1,4 @@
-FROM ubuntu:12.04
+FROM ubuntu:14.04

 ENV HOME /home/stackage
 ENV LANG en_US.UTF-8
@ -7,19 +7,19 @@ RUN mkdir /home/stackage -p
 RUN locale-gen en_US.UTF-8

 RUN DEBIAN_FRONTEND=noninteractive apt-get update
-RUN DEBIAN_FRONTEND=noninteractive apt-get install -y software-properties-common python-software-properties
+RUN DEBIAN_FRONTEND=noninteractive apt-get install -y software-properties-common python-software-properties git
 RUN DEBIAN_FRONTEND=noninteractive add-apt-repository ppa:hvr/ghc -y

 ADD debian-bootstrap.sh /tmp/debian-bootstrap.sh
 RUN DEBIAN_FRONTEND=noninteractive bash /tmp/debian-bootstrap.sh
 RUN rm /tmp/debian-bootstrap.sh

-RUN DEBIAN_FRONTEND=noninteractive apt-get install -y cabal-install-1.20 ghc-7.8.4 alex-3.1.3 happy-1.19.4
+RUN DEBIAN_FRONTEND=noninteractive apt-get install -y cabal-install-1.22 ghc-7.10.2 ghc-7.10.2-htmldocs alex-3.1.3 happy-1.19.4 sudo

-ENV PATH /home/stackage/.cabal/bin:/usr/local/sbin:/usr/local/bin:/opt/ghc/7.8.4/bin:/opt/cabal/1.20/bin:/opt/alex/3.1.3/bin:/opt/happy/1.19.4/bin:/usr/sbin:/usr/bin:/sbin:/bin
+ENV PATH /home/stackage/.cabal/bin:/usr/local/sbin:/usr/local/bin:/opt/ghc/7.10.2/bin:/opt/cabal/1.22/bin:/opt/alex/3.1.3/bin:/opt/happy/1.19.4/bin:/usr/sbin:/usr/bin:/sbin:/bin

 RUN cabal update
-RUN cabal install hscolour cabal-install --constraint "Cabal < 1.22" && cp $HOME/.cabal/bin/* /usr/local/bin && rm -rf $HOME/.cabal $HOME/.ghc /tmp/stackage
+RUN cabal install hscolour cabal-install && cp $HOME/.cabal/bin/* /usr/local/bin && rm -rf $HOME/.cabal $HOME/.ghc /tmp/stackage
 RUN wget https://s3.amazonaws.com/stackage-travis/stackage-curator/stackage-curator.bz2 && bunzip2 stackage-curator.bz2 && chmod +x stackage-curator && mv stackage-curator /usr/local/bin
-
-RUN cd /home/stackage && cabal update && stackage-curator check
+# Get new hyperlinked Haddocks
+RUN mkdir -p /opt/haddock && cd /opt/haddock && wget https://s3.amazonaws.com/download.fpcomplete.com/michael/haddock-2.16.2.tar.gz && tar zxf haddock-2.16.2.tar.gz && rm -f /opt/ghc/7.10.2/bin/haddock && ln -s /opt/haddock/2.16.2/bin/haddock /opt/ghc/7.10.2/bin/haddock
--- a/README.md
+++ b/README.md
@ -17,6 +17,21 @@ project information. In addition, we have the following repositories:
 * [stackage-curator](https://github.com/fpco/stackage-curator) [![Build Status](https://travis-ci.org/fpco/stackage-curator.svg?branch=master)](https://travis-ci.org/fpco/stackage-curator)
 * [stackage-types](https://github.com/fpco/stackage-types) [![Build Status](https://travis-ci.org/fpco/stackage-types.svg?branch=master)](https://travis-ci.org/fpco/stackage-types)
 * [lts-haskell](https://github.com/fpco/lts-haskell)
+* [stackage-nightly](https://github.com/fpco/stackage-nightly)
+
+We strongly recommend using the Haskell tool stack for doing builds, which
+includes built-in Stackage support:
+
+* [stack](https://github.com/commercialhaskell/stack) [![Build Status](https://travis-ci.org/commercialhaskell/stack.svg?branch=master)](https://travis-ci.org/commercialhaskell/stack)
+
+We also support some add-on tools to cabal-install to make its usage with
+Stackage both easier and more secure:
+
+* [stackage-cli](https://github.com/fpco/stackage-cli) [![Build Status](https://travis-ci.org/fpco/stackage-cli.svg?branch=master)](https://travis-ci.org/fpco/stackage-cli)
+* [stackage-update](https://github.com/fpco/stackage-update) [![Build Status](https://travis-ci.org/fpco/stackage-update.svg?branch=master)](https://travis-ci.org/fpco/stackage-update)
+* [stackage-upload](https://github.com/fpco/stackage-upload) [![Build Status](https://travis-ci.org/fpco/stackage-upload.svg?branch=master)](https://travis-ci.org/fpco/stackage-upload)
+* [stackage-install](https://github.com/fpco/stackage-install) [![Build Status](https://travis-ci.org/fpco/stackage-install.svg?branch=master)](https://travis-ci.org/fpco/stackage-install)
+* [stackage-build-plan](https://github.com/fpco/stackage-build-plan) [![Build Status](https://travis-ci.org/fpco/stackage-build-plan.svg?branch=master)](https://travis-ci.org/fpco/stackage-build-plan)

 Get your package included
 -------------------------
--- a/automated/.gitignore
+++ b/automated/.gitignore
@ -0,0 +1,10 @@
+/auth-token
+/bin/
+/gitconfig
+/hackage-creds
+/ssh-nightly/
+/ssh-lts/
+/nighlty/
+/lts-*/
+/stackage-curator/
+/stackage-update/
--- a/automated/build.sh
+++ b/automated/build.sh
@ -0,0 +1,82 @@
+#!/usr/bin/env bash
+
+set -eux
+
+ROOT=$(cd $(dirname $0) ; pwd)
+TARGET=$1
+TAG=$(echo $TARGET | cut -d- -f 1)
+IMAGE=snoyberg/stackage:$TAG
+
+if [ "$TAG" = "nightly" ]
+then
+    TROOT=$ROOT/nightly
+else
+    TROOT=$ROOT/$(echo $TARGET | cut -d. -f 1)
+fi
+
+PLAN_FILE=current-plan.yaml
+DOCMAP_FILE=current-docmap.yaml
+BUNDLE_FILE=current.bundle
+
+CABAL_DIR=$ROOT/cabal
+GHC_DIR=$ROOT/ghc
+DOT_STACKAGE_DIR=$ROOT/dot-stackage
+WORKDIR=$TROOT/work
+SSH_DIR=$ROOT/ssh-$(echo $TARGET | cut -d- -f 1)
+
+mkdir -p \
+	"$CABAL_DIR" \
+	"$GHC_DIR" \
+	"$DOT_STACKAGE_DIR" \
+	"$WORKDIR" \
+	"$SSH_DIR"
+
+GITCONFIG=$ROOT/gitconfig
+cat >$GITCONFIG <<EOF
+[user]
+	email = michael+stackage-build@fpcomplete.com
+	name = Stackage Build host
+EOF
+
+cat >$SSH_DIR/known_hosts <<EOF
+|1|Qn0iij8BnxGZXbyFSozS9zWkH+Q=|YrKKNp2KHO3/oc4UBFIe1zOvhDc= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
+|1|RxBEt2ljiEppr019szMIhbY12m0=|0FZ2Oji1LphRbPLLEQhFzTmL69I= ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEAq2A7hRGmdnm9tUDbO9IDSwBK6TbQa+PXYPCPy6rbTrTtw7PHkccKrpp0yVhp5HdEIcKr6pLlVDBfOLX9QUsyCOV0wzfjIJNlGEYsdlLJizHhbn2mUjvSAHQqZETYP81eFzLQNnPHt4EVVUh7VfDESU84KezmD5QlWpXLmvU31/yMf+Se8xhHTvKSCZIFImWwoG6mbUoWf9nzpIoaSjB+weqqUUmpaaasXVal72J+UX2B+2RPW3RcT0eOzQgqlJL3RKrTJvdsjE3JEAvGq3lGHSZXy28G3skua2SmVi/w4yCE6gbODqnTWlg7+wC604ydGXA8VJiS5ap43JXiUFFAaQ==
+EOF
+
+AUTH_TOKEN=$ROOT/auth-token
+HACKAGE_CREDS=$ROOT/hackage-creds
+
+function require_400_file {
+    if [ ! -f "$1" ]
+    then
+        echo File not found: "$1"
+        exit 1
+    fi
+
+    chmod 400 "$1"
+}
+
+require_400_file "$SSH_DIR/id_rsa"
+require_400_file "$AUTH_TOKEN"
+require_400_file "$HACKAGE_CREDS"
+
+mkdir -p $ROOT/bin
+BINDIR=$(cd $ROOT/bin ; pwd)
+(
+cd $BINDIR
+rm -f stackage-curator stackage-curator.bz2
+wget https://s3.amazonaws.com/stackage-travis/stackage-curator/stackage-curator.bz2
+bunzip2 stackage-curator.bz2
+chmod +x stackage-curator
+)
+
+ARGS_COMMON="--rm -u $USER -v $WORKDIR:/home/stackage/work -w /home/stackage/work -v $BINDIR/stackage-curator:/usr/local/bin/stackage-curator:ro -v /etc/passwd:/etc/passwd:ro -v /etc/group:/etc/group:ro"
+ARGS_PREBUILD="$ARGS_COMMON -v $CABAL_DIR:/home/stackage/.cabal -v $GHC_DIR:/home/stackage/.ghc -v $DOT_STACKAGE_DIR:/home/stackage/.stackage"
+ARGS_BUILD="$ARGS_COMMON -v $CABAL_DIR:/home/stackage/.cabal:ro -v $GHC_DIR:/home/stackage/.ghc:ro"
+ARGS_UPLOAD="$ARGS_COMMON -e AWS_ACCESS_KEY=$AWS_ACCESS_KEY -e AWS_ACCESS_KEY_ID=$AWS_ACCESS_KEY -e AWS_SECRET_KEY=$AWS_SECRET_KEY -e AWS_SECRET_ACCESS_KEY=$AWS_SECRET_KEY -v $AUTH_TOKEN:/auth-token:ro -v $HACKAGE_CREDS:/hackage-creds:ro -v $DOT_STACKAGE_DIR:/home/stackage/.stackage -v $SSH_DIR:/home/ubuntu/.ssh:ro -v $GITCONFIG:/home/stackage/.gitconfig:ro -v $CABAL_DIR:/home/stackage/.cabal:ro"
+
+# Use cabal update first to initialize ~/.cabal.config, then use stackage-curator update to get it securely
+docker run $ARGS_UPLOAD $IMAGE /bin/bash -c "stackage-curator check-target-available --target $TARGET"
+docker run $ARGS_PREBUILD $IMAGE /bin/bash -c "cabal update && stackage-curator update && stackage-curator create-plan --plan-file $PLAN_FILE --target $TARGET ${CONSTRAINTS:-} && stackage-curator check --plan-file $PLAN_FILE && stackage-curator fetch --plan-file $PLAN_FILE && cabal install random Cabal cabal-install"
+docker run $ARGS_BUILD $IMAGE stackage-curator make-bundle --plan-file $PLAN_FILE --docmap-file $DOCMAP_FILE --bundle-file $BUNDLE_FILE --target $TARGET
+docker run $ARGS_UPLOAD $IMAGE /bin/bash -c "stackage-curator upload-docs --target $TARGET --bundle-file $BUNDLE_FILE && stackage-curator upload-index --plan-file $PLAN_FILE --target $TARGET && stackage-curator upload-github --plan-file $PLAN_FILE --docmap-file $DOCMAP_FILE --target $TARGET && stackage-curator hackage-distro --plan-file $PLAN_FILE --target $TARGET"
--- a/build-constraints.yaml
+++ b/build-constraints.yaml
--- a/debian-bootstrap.sh
+++ b/debian-bootstrap.sh
@ -1,7 +1,7 @@
 #!/bin/bash -ex

 # Work in progress: create a list of commands necessary to get Stackage
-# up-and-running on a freshly installed Debian-based system (includin Ubuntu).
+# up-and-running on a freshly installed Debian-based system (including Ubuntu).

 # Quick start:
 # wget -O - https://raw.github.com/fpco/stackage/master/debian-bootstrap.sh | bash -ex
@ -10,50 +10,69 @@
 # instructions, see:
 #    http://www.stackage.org/install

-add-apt-repository -y ppa:chris-lea/zeromq
-add-apt-repository -y ppa:floe/libtisch
 add-apt-repository -y ppa:zoogie/sdl2-snapshots
+add-apt-repository -y ppa:marutter/rrutter
+add-apt-repository -y ppa:openstack-ubuntu-testing/icehouse
+
 apt-get update
 apt-get install -y \
    build-essential \
-    libncurses-dev \
-    git \
-    wget \
-    m4 \
-    texlive-full \
-    libgmp3c2 \
-    libgmp3-dev \
-    zlib1g-dev \
-    libedit2 \
-    libedit-dev \
    freeglut3-dev \
-    libglu1-mesa-dev \
-    libglib2.0-dev \
-    libcairo2-dev \
-    libpango1.0-dev \
-    libgtk2.0-dev \
-    zip \
-    libdevil-dev \
-    llvm \
-    libbz2-dev \
-    libjudy-dev \
-    libsqlite3-dev \
-    libmysqlclient-dev \
-    libpq-dev \
-    libicu-dev \
-    libssl-dev \
-    libgsl0-dev \
+    git \
+    libadns1-dev \
    libblas-dev \
-    liblapack-dev \
+    libbz2-dev \
+    libcairo2-dev \
    libcurl4-openssl-dev \
+    libdevil-dev \
+    libedit-dev \
+    libedit2 \
+    libfftw3-dev \
    libfreenect-dev \
-    libnotify-dev \
    libgd2-xpm-dev \
-    libyaml-dev \
+    libglib2.0-dev \
+    libglu1-mesa-dev \
+    libgmp3-dev \
+    libgsasl7-dev \
+    libgsl0-dev \
+    libgtk-3-dev \
+    libgtk2.0-dev \
+    libhidapi-dev \
+    libicu-dev \
+    libjudy-dev \
+    liblapack-dev \
+    libleveldb-dev \
    liblzma-dev \
+    libmagic-dev \
+    libmysqlclient-dev \
+    libncurses-dev \
+    libnotify-dev \
+    libopenal-dev \
+    libpango1.0-dev \
+    libpcap0.8-dev \
+    libphash0-dev \
+    libpq-dev \
    libsdl2-dev \
+    libsnappy-dev \
+    libsqlite3-dev \
+    libssl-dev \
+    libudev-dev \
+    libusb-1.0-0-dev \
+    libxau-dev \
+    libxml2-dev \
    libxss-dev \
-    libzmq3-dev
+    libyaml-dev \
+    libzmq3-dev \
+    llvm \
+    m4 \
+    nodejs \
+    npm \
+    r-base \
+    r-base-dev \
+    texlive-full \
+    wget \
+    zip \
+    zlib1g-dev

 mkdir /tmp/nettle-build
 (
--- a/stackage/ChangeLog.md
+++ b/stackage/ChangeLog.md
@ -0,0 +1,9 @@
+## 0.7.3.0
+
+* Added the executables split off from stackage-cli.
+
+## 0.7.0.0
+
+* First release of this incarnation of the stackage package. Previously, this
+  package provided completely different functionality. That functionality has
+  since moved to stackage-curator.
--- a/stackage/LICENSE
+++ b/stackage/LICENSE
@ -0,0 +1,20 @@
+Copyright (c) 2015 FP Complete
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be included
+in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
+CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
+TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
+SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
--- a/stackage/README.md
+++ b/stackage/README.md
@ -0,0 +1,2 @@
+This is a dummy wrapper package, forcing installation of other packages which
+provide real functionality.
--- a/stackage/Setup.hs
+++ b/stackage/Setup.hs
@ -0,0 +1,2 @@
+import Distribution.Simple
+main = defaultMain
--- a/stackage/Stackage/Dummy.hs
+++ b/stackage/Stackage/Dummy.hs
@ -0,0 +1,3 @@
+-- | This module does absolutely nothing. It's present so that cabal can more
+-- easily track whether the stackage package is installed.
+module Stackage.Dummy () where
--- a/stackage/stackage.cabal
+++ b/stackage/stackage.cabal
@ -0,0 +1,29 @@
+name:                stackage
+version:             0.7.3.2
+synopsis:            Dummy package forcing installation of other Stackage packages
+homepage:            https://www.stackage.org/
+license:             MIT
+license-file:        LICENSE
+author:              Michael Snoyman
+maintainer:          michael@snoyman.com
+category:            Development
+build-type:          Simple
+extra-source-files:  README.md ChangeLog.md
+cabal-version:       >=1.10
+
+library
+  exposed-modules:     Stackage.Dummy
+  build-depends:       base < 10
+                     , stackage-cli >= 0.1.0
+                     , stackage-update
+                     , stackage-upload
+                     , stackage-install
+                     , stackage-build-plan
+                     , stackage-cabal >= 0.1.1
+                     , stackage-sandbox >= 0.1.1
+                     , stackage-setup >= 0.0.1
+  default-language:    Haskell2010
+
+source-repository head
+  type:     git
+  location: git://github.com/fpco/stackage.git