Hooks (Carbs Linux User Manual)

From 374252a55c14f92aaed73b3917ed783bf2762911 Mon Sep 17 00:00:00 2001 From: Cem Keylan Date: Sat, 26 Dec 2020 03:23:39 +0300 Subject: docs: update --- docs/docs/Hooks.html | 103 --------------------------------------------------- 1 file changed, 103 deletions(-) delete mode 100644 docs/docs/Hooks.html (limited to 'docs/docs/Hooks.html') diff --git a/docs/docs/Hooks.html b/docs/docs/Hooks.html deleted file mode 100644 index e78cbf9..0000000 --- a/docs/docs/Hooks.html +++ /dev/null @@ -1,103 +0,0 @@ - - - - - - -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