[FFmpeg-devel] [DECISION] Project policy on closed source components

[Carl Eugen Hoyos]

Am Mo., 13. Mai 2019 um 22:32 Uhr schrieb James Almer <jamrial at gmail.com>:
>
> On 5/13/2019 5:23 PM, Carl Eugen Hoyos wrote:
> > Am Mo., 13. Mai 2019 um 22:18 Uhr schrieb James Almer <jamrial at gmail.com>:
> >>
> >> On 5/13/2019 5:13 PM, Carl Eugen Hoyos wrote:
> >>> Am Mo., 13. Mai 2019 um 22:10 Uhr schrieb Marton Balint <cus at passwd.hu>:

> >>>>> 1) Should libNDI support be removed from the ffmpeg codebase?
> >>>>
> >>>> Thanks for the votes, I counted 9 yes, 5 no, so majority is for removal of
> >>>> libNDI, which is already done.
> >>>
> >>> The vote was not about the removal from libndi from release branches?
> >>
> >> No, features on releases are frozen, as changing them can result in
> >> breakages for distros and package managers.
> >
> > We have broken distros and packages before, we would not break it
> > in this case;-)
>
> We would. Distros and scripts would be broken, and it would not be pretty.

Would you please be so kind as to explain (if possible in detail) how
this would be possible in this specific case?
I do not understand how removing a non-free dependency can break a
binary distribution.

> >> We have removed tons of
> >> libraries before and it's always limited to git master.
> >
> > None of them had to be removed because the authors chose to
> > violate our copyright (and refused to fix the copyright violation)
> > so we decided to stop endorsing them.
>
> If you feel strong about it

I don't, I just wonder how your interpretation of the question
is more obvious than mine.

> and if you think it justifies breaking
> releases and pissing off distros and package managers handling half a
> decade old well tested LTS releases, you can start a vote to remove it
> from releases.

Again: Please elaborate!

Carl Eugen