Earlier versions don't honour the -L/--library-path option,
which we need. See commit 4d0ccdad in gobject-introspection git.

Should "fix" build on lucid/maverick build bots.

GtkFunction is gone, and there's no update policies for
GtkRanges any more (but the default was continuous anyway,
so no need to set it to that mode explicitly).

https://bugzilla.gnome.org/show_bug.cgi?id=639215

Makes things work again properly in uninstalled setups (and
presumably in installed setups where GStreamer is installed
into a non-standard prefix). Requires fixes from core git.

https://bugzilla.gnome.org/show_bug.cgi?id=639039

Need to pass libgstreamer-0.10 explicitly to linker, since we're
calling gst_init(), which in turn is needed because the encoding
target get_type() function calls gst_value_register().

https://bugzilla.gnome.org/show_bug.cgi?id=639039

From e572c87 to f94d739

From ccbaa85 to e572c87

From 46445ad to ccbaa85

https://bugzilla.gnome.org/show_bug.cgi?id=639121

https://bugzilla.gnome.org/show_bug.cgi?id=638961

Make sure to use the PKG_CONFIG_PATH set at configure time instead of
just relying on an env-var set one. This makes sure both g-ir-compiler
and g-ir-scanner use the same PKG_CONFIG_PATH for determining include
paths etc.

We need them when building gir and typelib files for
libraries that depend on these, such as gst-rtsp-server
for example, in an uninstalled setup.

https://bugzilla.gnome.org/show_bug.cgi?id=638903

https://bugzilla.gnome.org/show_bug.cgi?id=638901

The unit tests are riddled with g_assert() and friends, sometimes
containing functional code like set_state() calls in them even
(looking at you, pipeline/capsfilter-renegotiation). Make sure we
don't disable assert and cast checks for the unit tests even if
this has been specified for the rest of the code base, e.g. via
--disable-glib-asserts.

Because we can, and because it's the most interesting one
to control really, after xpos/ypos.

https://bugzilla.gnome.org/show_bug.cgi?id=638859

This was causing keyframe_granule to be set to 0 for all streams
when seeking to the beginning of the stream, i.e., at the
beginning of playback.  Fixes #619778.

Instead, use either 0 or 1, depending on bitstream version, which give
the correct result for streams which aren't cut off at start.
This allows that function to not return negative granpos.

https://bugzilla.gnome.org/show_bug.cgi?id=638276

Some cosmetic changes and expands on some bits of the documentation to
make it more newbie-friendly.

The outgoing buffer timestamp is calculated by scaling an output buffer
count by the src pad frame rate caps. If these caps change, we need to
reset the count and work from a new base timestamp. The new output
buffer timestamp is then the count scaled by the new caps values added
onto the base timestamp.

Avoids escaping strings for nothing and printing out useless buffer contents.

Makes more sense name-wise

Along with a bunch of other internal cleanups