Seth Vidal wrote: > On Mon, 2008-09-08 at 15:28 -0500, Callum Lerwick wrote: >> On Mon, 2008-09-08 at 11:27 -0400, Jeremy Katz wrote: >>> And doing it this way would be more effective than cron as there are >>> plenty of people (especially with laptops/desktops which aren't on all >>> the time) for whom cron really isn't appropriate for anything that we >>> actually care to have done >> We still need to trigger pre-linking after yum transactions rather than >> by a cron job... > > > So we really need a generic yum-post-transaction trigger script. > > something that says: > > pkgname: action: command > > ie: > > glibc: *: /run/something/for/a/glibc/ > > > How do we determine which pkgs changing need a new prelink run? Shouldn't this be done on RPM level? Isn't this pretty much an extension of RPM triggers? Or it's so hard to do that that we now want to move stuff to yum? Similar issues that can be automatically handled also: - Run gtk-update-icon-cache if icons have been added/removed. - Run fc-cache if fonts have been added/removed. - Run ldconfig when share objects are installed (this one is done already, right?) It's really the same problem. Many of the RPM snippets we keep copying from package to package can be automated. I don't see how this one is different. behdad > I can put this together probably today if that's what's needed. > > -sv -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
