summary refs log tree commit diff
path: root/pkgs/development/haskell-modules/HACKING.md
diff options
context:
space:
mode:
author(cdep)illabout <cdep.illabout@gmail.com>2021-05-30 14:16:03 +0900
committer(cdep)illabout <cdep.illabout@gmail.com>2021-05-30 14:16:03 +0900
commit95e7f26425430ef4c9f176a84807cf4d0a4bd4ae (patch)
treef97e002de03247cf2ada9b268e1c03c6e5a3e20f /pkgs/development/haskell-modules/HACKING.md
parentadfec8b5e043dec328a4aaea9f5a43cc3ea0029f (diff)
downloadnixpkgs-95e7f26425430ef4c9f176a84807cf4d0a4bd4ae.tar
nixpkgs-95e7f26425430ef4c9f176a84807cf4d0a4bd4ae.tar.gz
nixpkgs-95e7f26425430ef4c9f176a84807cf4d0a4bd4ae.tar.bz2
nixpkgs-95e7f26425430ef4c9f176a84807cf4d0a4bd4ae.tar.lz
nixpkgs-95e7f26425430ef4c9f176a84807cf4d0a4bd4ae.tar.xz
nixpkgs-95e7f26425430ef4c9f176a84807cf4d0a4bd4ae.tar.zst
nixpkgs-95e7f26425430ef4c9f176a84807cf4d0a4bd4ae.zip
haskell-updates: update workflow documentation with a few small fixes
Diffstat (limited to 'pkgs/development/haskell-modules/HACKING.md')
-rw-r--r--pkgs/development/haskell-modules/HACKING.md28
1 files changed, 26 insertions, 2 deletions
diff --git a/pkgs/development/haskell-modules/HACKING.md b/pkgs/development/haskell-modules/HACKING.md
index 02085bdd806..8032614a408 100644
--- a/pkgs/development/haskell-modules/HACKING.md
+++ b/pkgs/development/haskell-modules/HACKING.md
@@ -221,8 +221,29 @@ causes all currently open Haskell-related pull-requests to be automatically clos
 
 Here are some additional tips that didn't fit in above.
 
--   It is possible to start a new Hydra evaluation by logging into Hydra with
-    your GitHub or Google account.
+-   Hydra tries to evalute the `haskell-updates` branch (in the
+    [`nixpkgs:haskell-updates`](https://hydra.nixos.org/jobset/nixpkgs/haskell-updates)
+    jobset) every 4 hours.  It is possible to force a new Hydra evaluation without
+    waiting 4 hours by the following steps:
+
+    1. Log into Hydra with your GitHub or Google account.
+    1. Go to the [nixpkgs:haskell-updates](https://hydra.nixos.org/jobset/nixpkgs/haskell-updates) jobset.
+    1. Click the `Actions` button.
+    1. Select `Evaluate this jobset`.
+    1. If you refresh the page, there should be a new `Evaluation running since:` line.
+    1. Evaluations take about 10 minutes to finish.
+
+-   It is sometimes helpful to update the version of
+    [`cabal2nix` / `hackage2nix`](https://github.com/NixOS/cabal2nix) that our
+    maintainer scripts use.  This can be done with the
+    [`maintainers/scripts/haskell/update-cabal2nix-unstable.sh`](../../../maintainers/scripts/haskell/update-cabal2nix-unstable.sh)
+    script.
+
+    You might want to do this if a user contributes a fix to `cabal2nix` that
+    will immediately fix a Haskell package in Nixpkgs.  First, merge in
+    the PR to `cabal2nix`, then run `update-cabal2nix-upstable.sh`.  Finally, run
+    [`regenerate-hackage-packages.sh`](../../../maintainers/scripts/haskell/regenerate-hackage-packages.sh)
+    to regenerate the Hackage package set with the updated version of `hackage2nix`.
 
 -   Make sure never to update the Hackage package hashes in
     [`pkgs/data/misc/hackage/`](../../../pkgs/data/misc/hackage/), or the
@@ -240,6 +261,9 @@ Here are some additional tips that didn't fit in above.
     [`regenerate-hackage-packages.sh`](../../../maintainers/scripts/haskell/regenerate-hackage-packages.sh)
     as described above.
 
+-   The Haskell team members generally hang out in the Matrix room
+    [#haskell-space:matrix.org](https://matrix.to/#/#haskell-space:matrix.org).
+
 ## Contributor Workflow
 
 (TODO: this section is to describe the type of workflow for non-committers to