Contents
Can a proprietary software be distributed without a LGPL license?
Yes, you can distribute your software without making the source code public and without giving recipients the right to make changes to your software. The LGPL license explicitly allows such usages of libraries/packages released under that license.
Which is the current version of the LGPL?
LGPLv3 is the current version of the GNU Lesser General Public License. LGPLv2.1 is an older version and not recommended by the Free Software Foundation for new projects anymore. Both licenses have the same intention, namely to protect the freedom of users to use and modify the software licensed under LGPL.
What’s the difference between a LGPL license and a license?
Both licenses have the same intention, namely to protect the freedom of users to use and modify the software licensed under LGPL. LGPLv3 makes this intention very explicit. You have to provide means to the end user to install a modified version of the library licensed under LGPLv3 and run your software using that modified library.
Is there a LGPL license for PySide2?
The thing is, PySide2 is for using the Qt framework with Python programs. Besides the LGPL license for PySide2, you’ll have to make sure that you comply with the Qt licensing terms.
What can you do with the LGPL license?
This license is mainly applied to libraries. You may copy, distribute and modify the software provided that modifications are described and licensed for free under LGPL.
Can You redistribute software under the LGPL?
You may copy, distribute and modify the software provided that modifications are described and licensed for free under LGPL. Derivatives works (including modifications or anything statically linked to the library) can only be redistributed under LGPL, but applications that use the library don’t have to be.
Is it possible to use the GNU LGPL covered library?
In short: yes you can. But one important thing to take care of is that the GNU LGPL covered library is dynamically linked, not statically mixed with the main application. It should also be possible to exchange that dynamically linked library for an independently compiled build.
What do I need to do if I use a LGPL licensed?
57 LGPL’s basic requirement is to separate the LGPL-licensed library and your own productwell enough. That should allow users to supply their own version of the library instead of the one you’ve shipped with your software (with the bugs fixed, for instance).