Add link. Clarify docs on getting a DockerHub build.

This commit is contained in:
Luke Murphy 2017-02-06 22:38:02 +01:00
parent c943b47ee3
commit bdaf428ade

View File

@ -23,8 +23,10 @@ process works:
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 "Adding Debian packages for required system tools or libraries"),
then block the package until it's fixed.
build later fails (see [Adding Debian packages]), then block the
package until it's fixed.
[Adding Debian packages]: https://github.com/fpco/stackage/blob/master/CURATORS.md#adding-debian-packages-for-required-system-tools-or-libraries
If benchmarks, haddocks, or test suites fails at this point we
typically also block the package until these issues are fixed. This in
@ -177,8 +179,14 @@ the maintainers of those packages.
### 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 to a branch should trigger a DockerHub. Normally only the `nightly` branch needs to be updated
since new packages are not added to the current lts release.
After you've committed those changes, merging them into the `nightly` branch should
trigger a DockerHub build. Simply run:
```bash
$ git checkout nightly
$ git merge master
$ git push
```
Use [Ubuntu Package content search](http://packages.ubuntu.com/) to determine which package provides particular dev files (it defaults to xenial which is the version used to build Nightly).