--disable-option-parsing changes semantics of gst_init_get_option_group() and breaks applications
It seems that --disable-option-parsing changes semantics of gst_init_get_option_group() and thus breaks applications. With --disable-option-parsing, gst_init_get_option_group() returns NULL without initializing GStreamer. Examples such as "The GOption interface" example at https://gstreamer.freedesktop.org/documentation/application-development/basics/init.html rely on the idea that gst_init_get_option_group() always initializes GStreamer.
Should we modify the implementation of gst_init_get_option_group() to initialize GStreamer even with --disable-option-parsing specified, albeit without GOptions? Or, perhaps should we more clearly document that it is the application's responsibility to call gst_init() if gst_init_get_option_group() returns NULL? The former seems more reasonable and robust, especially since gst_init_get_option_group() starts with "gst_init."
I suppose I might be missing something, but what I have found seems to leave things unclear.