Hooks (Carbs Linux User Manual)

From 4c3af89bc1de653a33dc0397a0dc1e63c6469cb8 Mon Sep 17 00:00:00 2001 From: Cem Keylan Date: Thu, 10 Sep 2020 14:00:02 +0300 Subject: update --- src/docs/Hooks.html | 95 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 95 insertions(+) create mode 100644 src/docs/Hooks.html (limited to 'src/docs/Hooks.html') diff --git a/src/docs/Hooks.html b/src/docs/Hooks.html new file mode 100644 index 0000000..113738b --- /dev/null +++ b/src/docs/Hooks.html @@ -0,0 +1,95 @@ + + + + + + +Hooks (Carbs Linux User Manual) + + + + + + + + + + + + + + + + + +

2.3 Hooks

+ +

Hooks can be used in order to change the runtime behaviour of the package manager. +There are a variety of package hooks, mostly self explanatory: +

pre-build +
post-build +
build-fail +
pre-test +
test-fail +
pre-install +
post-install +
pre-remove +
post-remove +
pre-fetch +
post-fetch +
post-package +

+ +

In order to use hooks, you will need to set the CPT_HOOK variable pointing +to your hook file. Your hook file MUST be a POSIX shell script as its +contents are sourced by the package manager. +

The hook is given 3 variables when it is executed. Those are: +

$TYPE: The type of the hook, (pre-build, post-build, etc.) +
$PKG: The package that cpt is currently working on. Can be null. +
$DEST: The destination of the operation. Can be null. +

+ + + + + + + + + + + -- cgit v1.2.3