From: Diego B. <di...@bi...> - 2005-10-31 10:29:47
|
On Sat, Oct 29, 2005 at 05:56:31PM -0600, Mike Melanson wrote: > Miguel Freitas wrote: > >On 10/29/05, Mike Melanson <mi...@mu...> wrote: > > > >> Should I commit it? I seem to recall some controversy about AAC > >>licensing changes. From what I can see, all of the source files still > >>have standard GPL headers on them, though with a stipulation non-GPL and > >>commercial non-GPL uses are prohibited. > > > >i remember the problem was something to do with requiring to display > >some copyright strings in application... anyway, this is pretty much > >grey area as gpl doesn't allow imposing further usage restrictions. > > > >my opinion: if they say it is gpl, we should trust them. just commit the > >thing. > > > >in case anybody has problems with faad2 licensing terms should please > >contact our lawyers. better yet: their lawyers ;-) Trusting Nero on this is a very bad idea, the advertising clause they came up with is GPL-incompatible. If you include this, it will extend to all of xine(-lib). > Hmm, I only see a stock GPL header. But this snapshot is over a year > old (latest "release" they offer for download). Maybe some newer version > has the problem. But this version seems to decode AAC just beautifully. The problem was introduced on 2005-02-01. I must say I'm quite perplexed to see you all handle license issues in such an easygoing fashion. MPlayer has the (at least nowaday completely undeserved) reputation of being lax towards licensing issue and this causes no end of grief when it comes to being included in distributions and similar things. Trust me, this is not a road you wish to tread upon. So please take a friendly piece of advice from me and keep a keen eye on licensing issues. Regards Diego |