-
Notifications
You must be signed in to change notification settings - Fork 0
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
License clarification #6
Comments
Hi Chris,
Under those circumstances, no. If integrating the c library into a compiled commercial product, then yes. But even that fee is minimal, unless I need to get heavily involved. Hope that answers the question.
Cheers, Matt

Matt Stead
***@***.***
… On Sep 26, 2024, at 1:46 PM, Chris Markiewicz ***@***.***> wrote:
Does MEDPython consider import dhn_med_py "linking" in the sense that any package that performs the import must be GPL-licensed?
This is the position taken by Mercurial (https://wiki.mercurial-scm.org/License), which requires non-GPL tools to use their CLI instead, so it's worth clarifying.
—
Reply to this email directly, view it on GitHub <#6>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATNKTHRGBXKYSKLO6AIVPTLZYRQCXAVCNFSM6AAAAABO5XE5Q6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGU2TCNBRGE3TOMQ>.
You are receiving this because you are subscribed to this thread.
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Does MEDPython consider
import dhn_med_py
"linking" in the sense that any package that performs the import must be GPL-licensed?This is the position taken by Mercurial (https://wiki.mercurial-scm.org/License), which requires non-GPL tools to use their CLI instead, so it's worth clarifying.
The text was updated successfully, but these errors were encountered: