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? 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
