[gstreamer-bugs] [Bug 513900] New: [registry] handle inconsistent state if duplicate plugins are removed?

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=513900

  GStreamer | gstreamer (core) | Ver: HEAD CVS
           Summary: [registry] handle inconsistent state if duplicate
                    plugins are removed?
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: Normal
         Component: gstreamer (core)
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: t.i.m at zen.co.uk
         QAContact: gstreamer-bugs at lists.sourceforge.net
                CC: t.i.m at zen.co.uk
 BugsThisDependsOn: 512740
     GNOME version: 2.21/2.22
   GNOME milestone: Unspecified


+++ This bug was initially created as a clone of Bug #512740 +++

See the above bug for some background. Setting:

 - core 0.10.17 + gst-plugins-base 0.10.15 installed in /usr

 - running 'make check' with local -base 0.10.17 build, which will
   create a local test-registry.xml file. The plugins path of the
   test environment is specified as LOCAL_PLUGINS:CORE_PLUGINS where
   core plugins includes the old 0.10.15 -base plugins. Now, later
   scanned plugin features in the registry will trump earlier ones,
   so the registry will end up with two plugin records for each
   duplicate -base plugin, but only one of those (in this case, the
   installed path) will have the element factories, and the other
   one will have no element factories. Now, if you uninstall the
   -base 0.10.15 in /usr and then run 'make check' again, the
   registry records for those plugins will be removed, along with
   the element factories. Left in the registry will be empty
   plugin records for the locally-built plugins without any
   factories. Timestamp+size will still be up-to-date though, so
   the registry will not attempt to re-scan those plugins, and
   as a result those element factories remain invisible/nonexistent.


Question is if we want to handle something like this or not. Opinions?


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=513900.