RPM Community Forums

Mailing List Message of <rpm-users>

Clarification of the way triggers do work

From: Tobias Gerschner <tobias.gerschner@gmail.com>
Date: Wed 14 Oct 2009 - 23:39:20 CEST
Message-ID: <ea7e82ce0910141439h7a1a25b6t1d765c033b4bb020@mail.gmail.com>
Hi,

I have a couple of packages were the use of triggers does not produce
the expected result. Probably my understanding of the trigger logic is
wrong. Sorry I am still using rpm 4.4.5 in production and not rpm5 as
I want to .

I have a package foo, which contains

%triggerin -- bar
ln -sf /path/file/from/foo /path/directory/from/bar

My expectations are:

1) Package foo is already installed. When package bar is being
installed the %triggerin scriptlet will be executed after the %post
scriptlet from package bar
2) Package bar is already installed. When package foo is being
installed the %triggerin scriptlet will be executed after the %post
scriptlet from package foo.

Is this correct or is this wrong ? The triggers only need to be
executed once to set symlinks on upgrade no action needs to be taken.

-- 
Tobias Gerschner
Yoper Linux - www.yoper.com

Knowing is not enough; we must apply. Willing is not enough; we must do.
Received on Wed Oct 14 23:46:48 2009
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.