[FFmpeg-user] ERROR: libmp3lame >= 3.98.3 not found

Carl Eugen Hoyos ceffmpeg at gmail.com
Sat Oct 28 23:37:36 EEST 2017


2017-10-28 22:29 GMT+02:00 Reindl Harald <h.reindl at thelounge.net>:
>
>
> Am 28.10.2017 um 22:21 schrieb Carl Eugen Hoyos:
>>
>> 2017-10-28 22:16 GMT+02:00 Reindl Harald <h.reindl at thelounge.net>:
>>
>>>> I consider "cleanup" (the word that you strangely cut from the
>>>> quotes) in our environment an abuse, please be so kind as
>>>> to avoid using it here
>>>
>>> it is your personal problem alone that you consider code-cleanup "abuse"
>>
>>
>> No, it is the claim of clean-up that lead to the very issues
>> you were - rightly! - complaining about
>
> no it just shows that as for any other software development project on
> planet earth ordinary users are supposed to use releases while delevopment
> works on trunk and stabilize the codebase for the next release but you
> refuse to understand that basics which are true everywhere but on this list
> for decades

There is a huge basic misunderstanding here.
I suspect you assume I want FFmpeg to be developed the way I describe it
but in fact I am just explaining that this very "stabilization" (that may happen
for many other projects, I don't know) simply does not exist here: I am here for
more than twenty main releases and every single one was just another
snapshot. The exact timing of the release was sometimes discussed (so
that patches were delayed or pushed) but no other tests than the daily
regression tests were done.
(In addition, I stopped asking for regression fixes before releases because
they were explicitely ignored / refused a few releases ago.)

> trunk is supposed to have issues from time to time and so your "trunk has
> *always* less errors" is simply a lie - it *may* fix a particular issue
> while it may also introduce unknown issues

It is not a lie, current FFmpeg does contain bugs but less than any release.

Carl Eugen


More information about the ffmpeg-user mailing list