On Sun, 2007-07-08 at 11:29 +0300, Panu Matilainen wrote: > On Fri, 6 Jul 2007, Toshio Kuratomi wrote: > > > On Fri, 2007-07-06 at 16:28 +0200, Phil Knirsch wrote: > >> > >> I really like that solution to be honest. It avoids lots of unnecessary > >> gtk-update-icon-cache calls during the update and only does it once at > >> the end. Could something similar be done for the scrollkeeper-update > >> calls as well btw? Or do they need to be done after each package install? > >> > > scrollkeeper is a little different. On package install it calls: > > scrollkeeper-update -q -o /usr/share/omf/NAME || : > > > > to process the just-installed omf file whereas ldconfig and > > gtk-update-icon-cache rescan all libraries or icons in a hierarchy. > > Well, that's how packages currently call it to avoid processing other > entries. But check 'scrollkeeper-update -v' - it actually processes all > the omf entries there by default, unless told otherwise. So this would > apply to scrollkeeper just as well. > I thought the cost of running scrollkeeper-update over all the omf files was higher. A quick test shows that it is comparable to ldconfig and gtk-update-icon-cache so you're right, we could call it at the end of all transactions. -Toshio
Attachment:
signature.asc
Description: This is a digitally signed message part
-- Fedora-maintainers mailing list Fedora-maintainers@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers
-- Fedora-maintainers-readonly mailing list Fedora-maintainers-readonly@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly
