~alpine/devel

1

[alpine-devel] apk info --triggers

Nathan Angelacos <nangel@nothome.org>
Details
Message ID
<4BF37448.1080901@nothome.org>
Sender timestamp
1274246216
DKIM signature
missing
Download raw message
What are apk --triggers?



---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Details
Message ID
<AANLkTinRjE4UGp5v7TvA_Ka7cuOmBEtCNe5o0MkMBqI6@mail.gmail.com>
In-Reply-To
<4BF37448.1080901@nothome.org> (view parent)
Sender timestamp
1274252407
DKIM signature
missing
Download raw message
On Wed, May 19, 2010 at 7:16 AM, Nathan Angelacos <nangel@nothome.org> wrote:
> What are apk --triggers?

Triggers are a feature in apk-tools. You can in a package say: when
anything changes in directory $d execute this script. For example,
busybox modprobe monitors /lib/modules/*, when there is a change in
there, 3rd party module or a kernel is installed or removed, the
trigger script will be executed and can do a depmod.

Rather than running depmod as a post-install script, once for every
affected package, it is run after all packages are installed, once.

Other usecase is font-cache. For each installed font the font cache
needs to be updated. This is pretty slow, so if you install many fonts
you win pretty much on updating the font cache once, after all fonts
are installed, rather than updating font cache for each installed
font.

Hope that explains.

-- 
Natanael Copa


---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---
Reply to thread Export thread (mbox)