1 |
On Tue, Nov 6, 2018 at 10:57 AM Alexis Ballier <aballier@g.o> wrote: |
2 |
> |
3 |
> On Tue, 06 Nov 2018 17:08:22 +0200 |
4 |
> Mart Raudsepp <leio@g.o> wrote: |
5 |
> |
6 |
> > It is not GStreamer fault that ffmpeg breaks API and ABI without |
7 |
> > parallel installability, much less so the distro maintainers of it. |
8 |
> > If you/upstream don't make it parallel installable, then this is what |
9 |
> > you get. |
10 |
> |
11 |
> Are you, seriously, suggesting this is the solution to all problems |
12 |
> here ? |
13 |
> |
14 |
|
15 |
It isn't the only solution, but it is one sane upgrade path. You |
16 |
can't expect everybody to update their software overnight when the API |
17 |
changes. That means you have to support the old API for a while when |
18 |
you introduce a new one, otherwise you end up with some software that |
19 |
doesn't work with the old version, and some software that doesn't work |
20 |
with the new version. |
21 |
|
22 |
Inevitably you get some program that is either simple or has a ton of |
23 |
manpower that refactors to the new API very quickly and abandons |
24 |
versions using the old API, and then you have some other program that |
25 |
is very complex or low-manpower that takes forever to adopt it. |
26 |
|
27 |
Now, parallel installation isn't the only way to accomplish this |
28 |
inter-compatibility, but it is one way. |
29 |
|
30 |
It seems like everybody is determined to go down the |
31 |
appimage/container path and just make dll-hell the new standard for |
32 |
linux. When every program gets bundled with its on zlib you don't |
33 |
have to worry about compatibility. Now you just get to update all 47 |
34 |
copies of it when a vulnerability turns up, and hope that the fix is |
35 |
backported to all 13 versions you're implicitly using. |
36 |
|
37 |
-- |
38 |
Rich |