From: GStreamer (bugzilla.gnome.org) <bug...@bu...> - 2008-04-01 12:15:37
|
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=520468 GStreamer | gstreamer (core) | Ver: 0.10.17 ------- Comment #22 from Stefan Kost (gstreamer, gtkdoc dev) 2008-04-01 12:15 UTC ------- < ensonic> __tim: what use case where you thinking of when suggesting to add _is_enabled() _set_enabled() to the registry-no-checking patch < __tim> ensonic: use case "call this before gst_init to disable registry update checking" < __tim> Having a magic environment variable for this doesn't seem quite right to me < ensonic> __tim: imho the usecase is to have it disabled by default and just run GST_CHECK_REGISTRY_CACHE=1 gst-inspect >/dev/null at startup and after installs < __tim> true, and some have setters and getters as well, e.g. gst_registry_fork_set_enabled() and gst_segtrap_is_enabled() < ensonic> __tim: instead of an env-var it could lso be an option < __tim> but I don't really care enough to argue about this at length to be honest ;) < ensonic> __tim: I prefer and option over two extra API entries that would be hardly called so lets use an option, unless someone has a usecase for apps, the API can be added later if needed. -- 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=520468. |