4 ms·
I find disallowing modifications to the SDK (under the GCFL) to be a really bizarre choice. Is this allowed with a paid license of some sort? If not, why not? I
by kevingadd 14y ago
I find disallowing modifications to the SDK (under the GCFL) to be a really bizarre choice. Is this allowed with a paid license of some sort? If not, why not? It's basically standard operating procedure in games that if the SDK you're using doesn't cut it, you work around the issues in order to ship. Is this specifically aimed at preventing people from using bizarre derivative forks of your toolset?
- AntiRush 14y agoThe spirit of the requirement is to encourage contributions back to the GPL version. You can fix or modify the GCFL version as needed - the only requirement is that you contribute back any changes to the SDK itself back to the GPL version. This way we can ensure that everyone benefits from having the latest and most bug-free code.
- kevingadd 14y agoI see, I read it as meaning that you can't use the GCFL version if you have any modifications that GC hasn't integrated into trunk. If it just means that you have to contribute the changes back under the GPL that's much simpler.