c24c213 · stackage · git.iko.soy

279

280## Local curator setup

281

282−We don't run the full stackage build locally as that might take too

282+We do not run the full stackage build locally as that might take too

283much time. Some steps on the other hand are much faster to do

284yourself.

285

286−It's useful to be able to modify constraints locally before pushing to

286+It is useful to be able to modify constraints locally before pushing to

287the repository. To do this first install stackage-curator:

288`git clone git@github.com:fpco/stackage-curator.git && cd stackage-curator && stack install`

289or get the linux binary: https://s3.amazonaws.com/stackage-travis/stackage-curator/stackage-curator.bz2

290−(it's a good idea to upgrade stackage-curator at least at the start of your week as curator).

290+(it is a good idea to upgrade stackage-curator at least at the start of your week as curator).

291Then clone the stackage repo `git clone git@github.com:fpco/stackage.git`.

292Inside it run `stack update && stackage-curator check` to get new packages and do dependency resolution.

293

295(including for test suites and benchmarks), to check whether bounds

296can be lifted, and to get `tell-me-when-its-released` notifications.

297

298−Notably this doesn't build anything, so you won't see any compilation

298+Notably this does not build anything, so you wont see any compilation

299errors for builds/tests/benchmarks.

300+

301+## Adding new curators

302+

303+1. Add public ssh key to build server

304+2. Add to fpco/stackage project.