3 ms·
I was astonished to see that Microsoft provided this software (R) under the terms of GNU GPLv2 or GNU GPLv3 explicitly (but not any later version)[0]. May be be
by pksadiq 8y ago
I was astonished to see that Microsoft provided this software (R) under the terms of GNU GPLv2 or GNU GPLv3 explicitly (but not any later version)[0]. May be because this is a derivative work from GNU R.
That's a good news for free software developers. Microsoft GVFS[1] was using MIT (while git itself is GNU GPLv2) + some EULA[2]. May be they chose MIT for GVFS because GNU GPL license explicitly disallows additional restrictions (ie, EULA can't be added, otherwise it will tbe a violation of GNU GPL).
Edit: I see that the package is distributed as a single binary at https://mran.microsoft.com/download https://mran.microsoft.com/download Which shall include (I haven't checked the contents) Microsoft R Open under GNU GPLv2 and Intel MKL with some EULA (ie, additional restrictions). Won't that be a violation of GNU GPLv2?
[0] https://mran.microsoft.com/faq#licensing https://mran.microsoft.com/faq#licensing
[1] https://github.com/Microsoft/GVFS https://github.com/Microsoft/GVFS
[2] https://github.com/Microsoft/GVFS/blob/master/GvFlt_EULA.md https://github.com/Microsoft/GVFS/blob/master/GvFlt_EULA.md
- DannyBee 8y agoNo, it's an aggregation which is fine. In more detail: packaging gpl and non gpl software next to each other is fine, even if your package format is a single binary. Linking mkl into gpl software and distributing the binary would not be okay because you don't have source to mkl you can give people (mkl has binary blobs). When you link software like this, you need to be able to distribute the combined binary under gpl, and unless mkl has changed, you can't. It would be fine to link it and use it locally of course, just not distribute it.