rpm5 triggers

[Jan Rękorajski]

On Wed, 28 Nov 2012, Elan Ruusamäe wrote:

> On 28.11.2012 18:14, Jeffrey Johnson wrote:
> > On Nov 28, 2012, at 11:01 AM, Elan Ruusamäe <glen at pld-linux.org> wrote:
> >
> >> where's the doc describing how triggers in rpm5 work? them seem to misbehave, ie $1 should be 1 on package first install, but my test shows that it is 0 with rpm5
> >>
> >
> > The doc is right where its always been: doc/triggers.
> 
> good, at least i'm not stupid then, expecting things to work and not 
> reading proper docs :)
> 
> for the record, no functional change in that file:
> $ diff -u triggers-rpm?
> --- triggers-rpm4    2007-05-25 20:35:58.000000000 +0300
> +++ triggers-rpm5    2008-02-18 02:40:45.000000000 +0200
> @@ -105,11 +105,11 @@
>   Trigger specifications are of the form:
> 
>   \verbatim
> -    %trigger{un|in|postun} [[-n] <subpackage>] [-p <program>] -- <trigger>
> +    %trigger{un|in|postun} [[-n] SUBPKGSUFFIX] [-p PROGRAM] -- TRIGGER
>   \endverbatim
> 
>   The -n and -p arguments are the same as for %post scripts.  The
> -<trigger> portion is syntactically equivalent to a "Requires"
> +TRIGGER portion is syntactically equivalent to a "Requires"
>   specification (version numbers may be used). If multiple items are
>   given (comma separated), the trigger is run when *any* of those
>   conditions becomes true (the , can be read as "or"). For example:
> (END)
> 
> 
> > You need to describe your test. Trigger behavior is
> > explicitly tested before every release at rpm5.org.
> yeah. it could be pld patches as well (baggins applied bunch of "useful 
> ones" from mandriva repository.

Nothing in those patches touch execution of triggers, so it must be
something in rpm5 itself that changed.

-- 
Jan Rękorajski                                 | PLD/Linux
SysAdm                                         | http://www.pld-linux.org/
baggins<at>mimuw.edu.pl
baggins<at>pld-linux.org