[gst-devel] Blocker bugs to apply tomorrow

Andy Wingo wingo at pobox.com
Mon Dec 5 02:17:01 CET 2005


Hi,

A bit of blocker bug status.

I was under the impression that carefully considered API changes could
still go in. Apparently that's not the case. Some of these blockers
can't be applied.

On Sun, 2005-12-04 at 23:22 +0100, Andy Wingo wrote:
> 319172 	gstreamer-plugins-base-0.9.pc doesn't export linking flags
>   -> Simple patch attached, looks good

Applied.

> 322874 	[PAD] pad_alloc_buffer should not call set_caps
>   -> The most difficult of all of these -- should add a new function 
>      that does what pad_alloc_buffer does now and sed all plugins to
>      call it, then do a proper fix later

There's a patch on the bug now -- need to sed all callers to use
gst_pad_alloc_buffer_and_set_caps.

> 322920 	[API] inconsistent usage of new_segment and newsegment an...
>   -> Need to sed API

Deferred for 0.11

> 322947 	[API] add GST_FLOW_DROPPED
>   -> Important need to allow for flowreturn extensibility

FLOW_DROPPED is not an error, it's positive -> no ABI change required;
changin numeric values of flowreturns to allow for extensibility a 0.11
change.

> 323017 	While(1) loop with sleep(0) in basertpdepayload.c
>   -> don't be terribly mean to kai

Waiting on a ping to determine which patch to use

> 323199 	Remove id3tag element (replaced by id3demux and id3mux)
>   -> very easy to remove now and add back later, impossible to remove
>      in the future

Done

> 323222 	GStreamer 0.9.7 still checks in dirs containing 0.9
>   -> simple patch looks good

Done

Regards,
-- 
Andy Wingo
http://wingolog.org/





More information about the gstreamer-devel mailing list