this will probably not be done, it's mostly used for development and when you do something special to an application, you can just give it the needed vars depending on what version of gst it is linked to.

This is to be coherent with the rest of the framework, it's just like you would be ignoring this as part of the ABI, even if it permits changing the plugin search path.

I'm not sure why you consider the env vars to be for development, but not the gst-launch-mm, or gst-inspect-mm binaries.

I don't understand this part: "you can just give it the needed vars depending on what version of gst it is linked to".


This bug is very minor to me, but I thought it should be noted that for some reason, this particular part of the ABI isn't versionned.  I'm not disturbed by this in any way, but thought this was simply forgotten.  This surprized me as what you pass in these env vars is typically not compatible (you don't pass a 0.8 plugin path to a 0.10 app).