On 5/31/07, David Schleef <[EMAIL PROTECTED]> wrote:
- Core checks a well known file (/var/cache/gstreamer-0.10 /plugin-timestamp) at the same time as all the .so file timestamps. If this timestamp is not the same as what is contained in the registry, the core forces a regeneration of the entire registry.
Of course regenerating the entire registry (possibly requiring loading a hundred of shared objects) is not needed in this bug, since we know precisely which plugin is affected. This might affect the system performance (we'll be making it do 100 times more work; performance matters!). - When a package is installed that might affect the contents of the
registry, but doesn't affect a relevant .so file, the post-install script should touch the plugin-timestamp file.
Not that I can think of such a case, but anyway, this bug talks about a single specific plugin. IMO, a complete solution involves ... GStreamer has a bug tracker and an open bug containing discussion on possible solutions. See my first post on this bug for a link.
