On 27.10.2016 00:16, Rostislav Pehlivanov wrote:
> On 26 October 2016 at 22:48, James Almer <jamr...@gmail.com> wrote:
>
>> On 10/26/2016 6:19 PM, Rostislav Pehlivanov wrote:
>>> Also removes url_feof from libavformat.v which should have been
>>> removed long ago and changed the multipart jpeg boundary tag to
>>> ffmpeg rather than ffserver (it's arbitrary).
>>
>> [...]
>>
>>> diff --git a/libavformat/libavformat.v b/libavformat/libavformat.v
>>> index c961cd8..47d5ddc 100644
>>> --- a/libavformat/libavformat.v
>>> +++ b/libavformat/libavformat.v
>>> @@ -1,19 +1,6 @@
>>> LIBAVFORMAT_MAJOR {
>>> global:
>>> av*;
>>> - #FIXME those are for ffserver
>>> - ff_inet_aton;
>>> - ff_socket_nonblock;
>>> - ff_rtsp_parse_line;
>>> - ff_rtp_get_local_rtp_port;
>>> - ff_rtp_get_local_rtcp_port;
>>> - ffio_open_dyn_packet_buf;
>>> - ffio_set_buf_size;
>>> - ffurl_close;
>>> - ffurl_open;
>>> - ffurl_write;
>>> - #those are deprecated, remove on next bump
>>> - url_feof;
>>> local:
>>> *;
>>> };
>>
>> No, this can't be done until the next major bump. url_feof is even guarded
>> by an scheduled FF_API define.
>>
>> The rest should be ok, but anything that implies a library ABI break can't
>> be done just yet. Wait for other comments and/or testing. This removes a
>> lot of things after all.
>>
> Fixed version attached without removing url_feof (apparently that's meant
> to go in the next bump, wasn't forgotten)
No, none of the symbols can be removed without a major bump. The simple reason
is that a ffserver built from the 3.1 branch still has to work with the
libavformat from the 3.2 branch.
Best regards,
Andreas
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
