Differences
This shows you the differences between the selected revisions of the page.
2016-05-24 | 2016-10-08 | ||
many people require explanation why it is possible to use the .net assembly under mit license despite the applkication using gpl license (martin) | rephrased it (sentences with 4 commas...) , removed unneeded details - that is using the public scripting interface is not a detail which matter in the license. Also if a text is using "simply said", well then maybe the text is not that good. (Julian304) | ||
Line 189: | Line 189: | ||
The WinSCP .NET Assembly is a free library: you can use it, redistribute it and/or modify it under the terms of the [[https://www.mozilla.org/MPL/2.0/|Mozilla Public License Version 2.0]]. | The WinSCP .NET Assembly is a free library: you can use it, redistribute it and/or modify it under the terms of the [[https://www.mozilla.org/MPL/2.0/|Mozilla Public License Version 2.0]]. | ||
- | Note that [[library_install#installing|the assembly interacts with WinSCP executable]], which uses a [[license|different license, the GPL]]. Though as WinSCP is used as an executable, via its public [[scripting|scripting interface]], not as a library, all you need to do to comply with the GPL license, is to keep %%GPL%% license file around.((Simply said, keep all files from ''winscpXXXautomation.zip'' package together.)) | + | Because WinSCP uses [[license|the GPL license]] it's important to keep the %%GPL%% license file around. Your software doesn't have to be licensed under GPL as the WinSCP .NET Assembly is using WinSCP as an executable and not as a library. |