Hi, Bill:
I've seen this page. I used to consult whether LGPLed code is
compatible with ASL, and people in Apache community show me this link:
http://www.apache.org/legal/resolved.html. I found the following words:
GNU LGPLThe LGPL is ineligible primarily due to the restrictions it places
on larger works, violating the third license criterion. Therefore,
LGPL-licensed works *must not* be included in Apache products. After seeing
that, i believed that we need to replace FFmpeg. So far as i know, we only
use libavcode and libavformat from FFmpeg. As to libpostproc and/or
libswscale, i would ask Jiang Shan to confirm whether we use these libs. I
will send you the result soon.
It would be quite awkward if thing goes like this..........
regards,
Kevin
2009/7/24 Bill Stoddard <[email protected]>
> Bluesky team...
> Can you share your latest status with making Bluesky compliant with the
> Apache License? I know one package you were interested in was ffmpeg. Have
> you seen this link?
>
> http://ffmpeg.org/legal.html
>
> "FFmpeg is licensed under the GNU Lesser General Public License (LGPL)
> version 2.1 or later. However, FFmpeg incorporates several optional modules
> that are covered by the GNU General Public License (GPL) version 2 or later,
> notably libpostproc and libswscale. If those parts get used the GPL applies
> to all of FFmpeg."
>
>
> Does bluesky need libpostproc and/or libswscale? If not, then bluesky can
> dynamically link into ffmpeg and still be in compliance with the Apache
> License.
>
> Bill
>
--
Bowen Ma a.k.a Samuel Kevin @ Bluesky Dev Team XJTU
Shaanxi Province Key Lab. of Satellite and Terrestrial Network Tech
http://incubator.apache.org/bluesky/
