Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should license be LGPLv3 instead of GPLv3? #14

Open
humbleengineer opened this issue Mar 25, 2024 · 0 comments
Open

Should license be LGPLv3 instead of GPLv3? #14

humbleengineer opened this issue Mar 25, 2024 · 0 comments

Comments

@humbleengineer
Copy link

As it stands (and to my understanding of the GPL), any Python program or package using blkinfo with its current GPLv3 license must be made available in its entirety as source code. That prevents a barrier to use of blkinfo.

I think the most Python packages that use a GPL variant use LGPL. With LGPL, if I included a modified version of blkinfo in a proprietary program then I would need to make the modified blkinfo source available, but not all the rest of the proprietary code. For example, psycopg2 uses LGPL

What's the intent here? If it is full GPL that's fine, but I thought I'd ask.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant