JWPlatt wrote:I would appreciate it if anyone from the GoW could, before I work on it this weekend, summarize the libraries you believe need GPLv3 exceptions to distribute the client and plugin builds to make sure we're including them.
Please post your contributions to the OU thread.
My apologies for sounding rude, but shouldn't you know this?
You're the people supposed to be acting as shepherds for open-source; you're the people through whom Cyan has made it clear they will be exclusively pulling fixes; you're the people that are managing all of this open-source stuff... and you don't know what the dependencies of your project are? You don't know which ones are GPL-compatible and which ones aren't?
Have any of you actually built Plasma, or have you been more interested in setting up enterprise managerial tools that most developers hate and see as a waste of time?
I realize this is a hobby, everyone is busy, etc... that includes all of us too.
I'm not sure why you seem to think "out-sourcing" things to us is a good use of our time, rather that you actually learning something about the project you're in charge of.
Not to be entirely unhelpful, the 3 big issues are:
- PhysX cannot be linked against the GPL (any version of it) with an exclusion
- Bink cannot be linked against the GPL without an exclusion
- It is impossible to have a GPL-licensed 3DS Max plugin without an exception, because it would force all of Max to be GPL
A lesser issue is OpenSSL, which only poses problems on Windows (on Linux it's considered a system library, I think Mac too but I'm not entirely sure). It's probably best to explicitly add an exception allowing linking against OpenSSL just to prevent any issues from cropping up.
"And one day I woke to find the future held no place for me. I was unwanted in a world, that with my hands I'd helped to build. Where once was honesty and pride, I now stand broken and alone."