[FFmpeg-devel] [PATCH 1/2] lavf/avio: Extend API with avio_move() and avio_delete()
derek.buitenhuis at gmail.com
Tue Jun 23 01:09:19 CEST 2015
On 6/22/2015 11:58 PM, Mariusz Szczepańczyk wrote:
> I don't think it's fair to say Lukasz is the only one standing for these
> changes. But let's not make it personal and hold on any grudges for a
I hold no ill will against anyone, as long as no ill will is held against me.
I do, however, think it was pretty dishonest of some people to push this
forward as a GSOC project when there was internal dissent for it (on IRC,
on the ffmpeg-mentor list, etc.). This is of course not your problem,
nor should it be. We're here now, so we should make the best of it.
> My point is that ongoing fights like this are counterproductive and only
> discourage people from contributing into open source. I also think everyone
> wants the best for the project regardless they are pro or against the
> I see the current situation is as follows: there is increasing amount of
> code in libav* that you and some others find out of place. This is
> obviously not good.
> Is there any viable solution not involving removing functionality from
> ffmpeg would you agree on and make adding changes like this less painful?
> What do you think about making a temporary fork, moving things around there
> and showing something that is satisfactory to you?
The crux of the issue here is that there is disagreement on whether some features
should be in libav* at all. It's separation of functionality. It's not really
possible to show something satisfactory when it's the wrong place for it in
the first place, in someone's mind. I speak for myself here, only, of course.
Take it with a grain of salt.
As far as I see this situation, the damage is done already (it's in libav*), so we
may as well make it (the API) as decent as possible.
(P.S. I wouldn't use the word fork here, people get angsty :P)
More information about the ffmpeg-devel