If you change any of the LGPL code, you must make those changes available, but your own propriety code is safe, and you do not have to release it in any way. LGPL can be distributed with pay-for software. The main difference in GPL and LGPL code is that GPL must only go out with free software. However there is no obligation for you to provide source-code of your application as long as it is a work fully under your control and not a derivate of any of the LGPL'ed code. Look for requirements for a "work that uses the library." as yours would be. But this means you need to fullfill some needs as well. The GNU Library or Lesser Genreal Public License (LGPL) allows redistribution of binary form along with your (non LGPL'ed or non GPL'ed) application. WineskinLauncher is licensed under GNU LGPL 2.1Īfter this short review I would say that both Wine and Wineskin are available under the GNU LGPL 2.1 license.Wineskin Winery is licensed under GNU LGPL 2.1.Wineskin is licensed under GNU LGPL 2.1.The projects sourceforge page say it's "GNU Library or Lesser General Public License (LGPL)", not version information given.Wineskin's license - as far as I can see - is not clearly documented.On the other hand, a lawyer can tell you what you can do/what not regardless of what others say.
However, if you get permission by the original author(s), you're always fine. But as far as I can assume that is not automatically a link.Īs others have commented: When in doubt you have got two things to do: Get in contact with the original author(s) and ask for permission (easy) and second get in contact with a lawyer who can explain you everything in detail (harder).
WINESKIN WINERY NOT WORKING SKIN
If it's a community thing, you can think about to open source your skin so that users of your application can provide improvements more easily. Only if you modify wineskin or wine itself, you need to publish your changes if you distribute the changed binaries of wineskin or wine. So the same for your application: Only because you use a feature of some other application it does not mean that everything that gets in touch with that other application must be under the same license.
WINESKIN WINERY NOT WORKING SOFTWARE
osx) ) are mostly proprietary software not comming even close to a licensing in the sense of the LGPL. That by the way would render wine useless: Things it has been made for, like executing windows applications on a free (debian) or even more evil systems (e.g. So the licensing of wine and wineskin is for their own software only, but not for software wrapped by wine.įor example, the windows tetris game I copied over to my linux box must not be put under LGPL only because I run it under wine. As far as I know how wine works, it does not modify the programs itself, but provides a wrapper to make them more portable.
0 kommentar(er)
