[FFmpeg-cvslog] r21731 - in branches/0.5: . Changelog doc/APIchanges libavcodec/avcodec.h libavcodec/utils.c

[Reinhard Tartler]

On Mi, Feb 10, 2010 at 16:00:26 (CET), Ramiro Polla wrote:

>> Do you have one or more specific examples of applications that check the
>> LIBAVCODEC_VERSION_MINOR setting?
>
> vlc.git$ grep -r LIBAVCODEC_VERSION_INT * | wc -l
> 38

vlc.git$ grep -r LIBAVCODEC_VERSION_MINOR * | grep 21 | wc -l
0

>> As indicated in my previous post, when considering the relevant upgrade
>> paths, I don't think this is currenly a problem.
>>
>> I agree that changes like this could open pandora's box if used
>> carelessly, though.
>
> I don't think upgrade paths should have any effect on the issue here.
> Uoti's example shows very well an use that may break.

Okay, so the argument is that someone might use LIBAVCODEC_VERSION_INT
to check if the corresponding change in trunk is included or not:

------------------------------------------------------------------------
r17823 | schreter | 2009-03-05 08:35:06 +0100 | 3 lines

Add handling of frame position in the parser.

Luckily, this doesn't happen in vlc, but there is some risk that there
might be other projects that rely on that. Personally, I think taking
this risk has more benefit for the 0.5 branch than dropping this
patch. Ideally, there is another way to express this addition and I'm
open for suggestions.
                                                                                                                         
> Diego, how do you suggest we deal with version numbers in the releases?

CC'ing Diego, he mentioned that he doesn't follow the lists currently...


-- 
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4