Re: [FFmpeg-devel] [ANNOUNCEMENT] almpeg

["softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>]

> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Michael
> Niedermayer
> Sent: Montag, 26. Mai 2025 19:21
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [ANNOUNCEMENT] almpeg
> 
> Hi
> 
> On Mon, May 26, 2025 at 12:21:24PM +0000, softworkz . wrote:

[..]

> > I'm not sure how others see it, but I'd rather wait a bit for certain
> > features (as LGPL) than getting the project contaminated with GPL code.
> > And when you really need something, you can still cherry-pick it anyway.
> 
> but we dont really contaminate anything with GPL code

This is also related to the one-way relationship between LGPL and GPL:
Assuming all file headers are properly set up to indicate GPL, when you 
would merge a fix from him into FFmpeg - even when it's for example a filter 
developed by himself earlier and was provided under LGPL - if you merge that 
fix (under GPL) into the FFmpeg filter source file (LGPL), the filter will
no longer be LGPL but turn into GPL by merging the GPL fix.

That's what I mean by saying that FFmpeg would become contaminated by 
GPL code.

Best
sw

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".