From af5401ffceeae548ec42cfc6e1cf587c154b2830 Mon Sep 17 00:00:00 2001
From: Leonid Pliushch <leonid.pliushch@gmail.com>
Date: Tue, 5 Oct 2021 23:53:47 +0300
Subject: [PATCH] CONTRIBUTING.md: clarification on package updates

---
 CONTRIBUTING.md | 18 +++++++++++++++---
 1 file changed, 15 insertions(+), 3 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 0f32ff160..918b0f96a 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -208,9 +208,21 @@ More about `build.sh` variables you can read on [developer's wiki](https://githu
 You can check which packages are out-of-date by visiting Termux page on
 [Repology](https://repology.org/projects/?inrepo=termux&outdated=1).
 
-Most of packages can be updated by just modifying variables `TERMUX_PKG_VERSION`
-and `TERMUX_PKG_SHA256`, which represent the package version and checksum for
-source code archive respectively.
+### General package update procedure
+
+Usually to update packages you need to just modify few variables and commit
+the changes.
+
+1. Assign the new version value to `TERMUX_PKG_VERSION`. Be careful to not
+   remove the epoch (numbered prefix, e.g `1:`, `2:`) accidentally.
+2. If there is `TERMUX_PKG_REVISION` variable set, remove it. Revision
+   should be set only for subsequent package builds within the same version.
+3. Download the source code archive and compute SHA-256 checksum:
+   ```
+   cd ./packages/${YOUR_PACKAGE}
+   (source build.sh 2>/dev/null; curl -LO "$TERMUX_PKG_SRCURL")
+   ```
+4. Assign the new checksum value to `TERMUX_PKG_SHA256`.
 
 ### Dealing with patch errors