1 |
On 2018-11-06 11:21 a.m., Alexis Ballier wrote: |
2 |
> On Tue, 6 Nov 2018 11:09:17 -0500 |
3 |
> Rich Freeman <rich0@g.o> wrote: |
4 |
> |
5 |
>> On Tue, Nov 6, 2018 at 10:57 AM Alexis Ballier <aballier@g.o> |
6 |
>> wrote: |
7 |
>>> |
8 |
>>> On Tue, 06 Nov 2018 17:08:22 +0200 |
9 |
>>> Mart Raudsepp <leio@g.o> wrote: |
10 |
>>> |
11 |
>>>> It is not GStreamer fault that ffmpeg breaks API and ABI without |
12 |
>>>> parallel installability, much less so the distro maintainers of |
13 |
>>>> it. If you/upstream don't make it parallel installable, then this |
14 |
>>>> is what you get. |
15 |
>>> |
16 |
>>> Are you, seriously, suggesting this is the solution to all problems |
17 |
>>> here ? |
18 |
>>> |
19 |
>> |
20 |
>> It isn't the only solution, but it is one sane upgrade path. You |
21 |
>> can't expect everybody to update their software overnight when the API |
22 |
>> changes. That means you have to support the old API for a while when |
23 |
>> you introduce a new one, otherwise you end up with some software that |
24 |
>> doesn't work with the old version, and some software that doesn't work |
25 |
>> with the new version. |
26 |
> |
27 |
> |
28 |
> These days, only symbols/constants that have been deprecated (and |
29 |
> marked as such) for a couple of releases are removed. This means people |
30 |
> see warnings for more than one year before seeing them gone for good. |
31 |
> The problem here is not "overnight changes" but rather consumers not |
32 |
> paying attention to those warnings, or worse, nobody ever seeing those |
33 |
> because it's unmaintained. |
34 |
> |
35 |
|
36 |
But we aren't upstream most of the time, and if upstreams are pegging |
37 |
their ffmpeg to a single version they don't bother to try the newer |
38 |
one to find out the errors. Take Kodi, v17.x is pegged to no newer |
39 |
than ffmpeg-3.3.x as I recall, and has been blocking even v3.4's |
40 |
installation for the year'ish it's been in the gentoo repo. |
41 |
|
42 |
So this "people see warnings" thing, it really doesn't apply, unless |
43 |
you (A) have the desire and resources to build and maintain a patch |
44 |
for upstream, and (B) have an upstream with the desire and resources |
45 |
to support more than the one version of ffmpeg for a given release |
46 |
set. Both, IMO, are in very short supply. |