LGPL License is problematic

[esDotDev]

Due to the implementation of AIR on iOS, all code is compiled into the application, meaning we are essentially distributing a binary of your lib, which according to GPGL requires that we release entire source code of our applications, even if we have never modified your source code at all.

Any thoughts on switching to something less restrictive?

[CaptainN]

Hi Eugene!

Would it be possible to add the iOS exception clause to the license? I have the same issue as above, and I'm unsure about whether that exception is in the license or not.

Here's more info on the problem and what I mean by the iOS exception:
http://multinc.com/2009/08/24/compatibility-between-the-iphone-app-store-and-the-lgpl/

It's basically an added clause that lets users statically link to the library when the platform requires it (as on iOS), but still retains the rest of the terms of the LGPL, which is great.

Thanks,

Kevin N.

[CaptainN]

Just to flesh that out a bit more, I don't care if I have to offer binary objects, or even the source of my app to be compliant with LGPL - the issue is, I don't know how I'd do that for the actual AIR binary, or even if I'm allowed to do that (if I can, that'd solve the problem). A linking exception would make using this sweet library much easier.

[inspirit]

hey guys, i think i will change license type to MIT so u can do what ever u want with it. is it enough?

[esDotDev]

Perfect :)

[eamonnfaherty]

Hey inspirit,

Thank you for your contribution! I was wondering if you were able to update the licence file to MIT. We would like to use the library but are in a similar position. I can open a pull request if that helps?

Eamonn