GNOME Bugzilla – Bug 773089
gstreamer: set env GST_REGISTRY_DISABLE=yes to disable registry
Last modified: 2016-11-01 18:32:23 UTC
Setting the environment variable GST_REGISTRY_DISABLE=yes gives similar functionality as to compiling with GST_DISABLE_REGISTRY. The benefit is that the registry can be programmatically disabled by the application before calling gst_init() while keeping the registry enabled when using gst-launch etc.
Created attachment 337837 [details] [review] gstreamer: set env GST_REGISTRY_DISABLE=yes to disable registry If GST_REGISTRY_DISABLE=yes the registry is disabled similar to compile time switch GST_DISABLE_REGISTRY.
Does it make sense to have an env var for this then rather than dedicated API such as gst_disable_registry() or so?
Although an API would also work, I think an env var is more consistent with the current way such things are controlled by the application / user: * There are already env vars such as GST_REGISTRY, GST_REGISTRY_UPDATE, GST_REGISTRY_FORK etc. GST_REGISTRY_DISABLE is consistent with these. * If it's an API we introduce a gst-function that must be called before gst_init() in order to have an effect.
Fair enough. Can always add API later.
commit fd728c253139daa1ced5fdedf78540ee14a9f480 Author: Stian Selnes <stian.selnes@gmail.com> Date: Thu May 2 10:09:29 2013 +0200 registry: set env GST_REGISTRY_DISABLE=yes to disable registry If GST_REGISTRY_DISABLE=yes the registry is disabled similar to compile time switch GST_DISABLE_REGISTRY. https://bugzilla.gnome.org/show_bug.cgi?id=773089