haskell/stackage
1
0
Fork 0
mirror of https://github.com/commercialhaskell/stackage.git synced 2026-02-03 18:10:26 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

CURATORS.md: adding Debian packages to the build docker image

Browse Source
This commit is contained in:
Jens Petersen 2015-09-08 17:31:56 +09:00
parent 9923ae1bb7
commit 01ecbdce1d
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
CURATORS.md
View File

@ -38,12 +38,20 @@ to refer to the issue for workarounds added to that file.
* __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. * __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 * __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
## Upgrading GHC versions ## 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.
### Upgrading GHC version
The Dockerfile contains information on which GHC versions should be used. You 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 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. Once a new Docker branch is used for nightlies, and the lts branch for LTS.
image is available, you'll need to pull it onto the stackage-build server (see
### 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 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: delete all of the old images and let the new ones get downloaded:
@ -52,7 +60,7 @@ docker rm $(docker ps -a -q)
docker rmi $(docker images -q) docker rmi $(docker images -q)
``` ```
You should also delete the cache directories on the stackage-build server to 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). force all packages to be rebuilt. See: [issue#746](https://github.com/fpco/stackage/issues/746).
## stackage-build server ## stackage-build server