http://qa.mandrakesoft.com/show_bug.cgi?id=6360
------- Additional Comments From [EMAIL PROTECTED] 2003-11-15 11:13 -------
Apart this, before modifying any triggers, one have to test all the
cases, when EITHER the main or the triggerred package is "installed",
"uninstalled" or "upgraded". So you have a totally of ninecases; if I
remember right, the %triggerun
%triggerun -- <plugin>
[ "$1" = "0" ] || exit 0
if [ -L %{mozillaplugindir}/<plugin>.so ]; then
rm -f %{mozillaplugindir}/<plugin>.so
fi
is there because the %triggerun (at least in the past was so)
is ALSO called when the MAIN package is "upgraded", so you have to
SKIP the removing of the LINK in this case, and since the
same %triggerun weren't change since mozilla 1.2.1, I don't understand,
why in the past it worked, and shouldn't now?
--
Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
------- Reminder: -------
assigned_to: [EMAIL PROTECTED]
status: UNCONFIRMED
creation_date:
description:
When mozilla package is updated, the triggers of the package remove links from
/usr/lib/mozilla/plugins, e.g. the one for flashplayer.
Looking at the triggers one sees:
%triggerun ...
[ "$1" = "0" ] || exit 0
This is probably wrong, it should be:
%triggerun ...
[ "$2" = "0" ] || exit 0
^
This is also in the examples of /usr/share/doc/rpm-4.2/triggers and makes more
sense, because we care about what happens with the target package ($2), not our
package ($1).
