[gst-devel] clashing caps details

Stefan Kost ensonic at hora-obscura.de
Thu Nov 16 18:33:08 CET 2006

Hi Ville,

Ville Syrjala wrote:
> On Wed, Nov 08, 2006 at 02:05:52PM +0100, ensonic wrote:
>> hi,
>> please have a look at those there entries
>> [1] http://bugzilla.gnome.org/show_bug.cgi?id=361636
>> [2] http://bugzilla.gnome.org/show_bug.cgi?id=361637
>> [3] http://bugzilla.gnome.org/show_bug.cgi?id=363118
>> problems are now summarized in [1]. Unfortunately [3] has been committed 2
>> days ago and might need to be reverted/adjusted to avoid clashing with the
>> undocumented 'variant' usage for h263version (plus and plus plus).
>> Any ideas for naming and especily resolving the conflicts without API
>> breakage?
> AFAICS gst-ffmpeg hasn't been released with the undocumented 'variant'
> usage so I'm not sure if the API breakage is such a bad thing.
Oh yes, thats right. Committed now.
>> Any ideas how to catch this in the future? Getting a list of caps that
>> plugins use and ... ? How could we automatically figure out that a caps
>> detail is used multiple times for different purpose?
> A strict policy that no API breaking feature may be commited without
> discussion on the mailing list could be enough.
I meant, catching clashing caps strings. I've cooked something that
hooks into media-test suite and gathers all caps. This is not bullet
proof but better that nothing.


More information about the gstreamer-devel mailing list