From ea938ab17ab4163f68499cf974f1475a01719358 Mon Sep 17 00:00:00 2001 From: "Joshua M. Boniface" Date: Sat, 3 Dec 2022 02:01:06 -0500 Subject: [PATCH] Better clarify postrm deliniation --- content/debian-packaging-101.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/debian-packaging-101.md b/content/debian-packaging-101.md index a3da1a0..bae13ee 100644 --- a/content/debian-packaging-101.md +++ b/content/debian-packaging-101.md @@ -500,7 +500,7 @@ Each script has `set -o errexit` enabled by default; thus any failure of any ste * `prerm` runs during package removal, before the actual files of the program are removed. This is the second most common maintainer script, often used to de-configure services, remove users, remove created directories, etc. -* `postrm` runs during package remove, after the actual files of the program are removed. Really, anything that goes in `prerm` could likely also go in `postrm`, but where you put tasks depends on the specifics of your program. +* `postrm` runs during package remove, after the actual files of the program are removed. Some tasks in `prerm` could likely also go in `postrm`, but where you put tasks depends on the specifics of your program and what the script is doing, e.g. stop servers in `prerm` but remove directories in `postrm`. In very simple programs, you might not need any of these scripts, or might only need one or two of them. For our example we'll only need `postinst` and `prerm` to handle our service and user.