Better clarify postrm deliniation

This commit is contained in:
Joshua Boniface 2022-12-03 02:01:06 -05:00
parent e267456952
commit ea938ab17a
1 changed files with 1 additions and 1 deletions

View File

@ -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. * `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. 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.