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

Licence doubt #55

Open
jcfr85 opened this issue Nov 12, 2019 · 1 comment
Open

Licence doubt #55

jcfr85 opened this issue Nov 12, 2019 · 1 comment

Comments

@jcfr85
Copy link

jcfr85 commented Nov 12, 2019

Can i copy the project to another project and use directly the .h and .c importing the .h file in a non-free software?
There are some limitations to do this?

@RobSanders
Copy link
Collaborator

Obligatory initial statement - I am not a lawyer, nor is this legal advice. You need to be comfortable with the requirements of any licensing obligations or consult legal counsel for advice.

That being said, we are using the libcli in our commercial software (Linux based). Our approach has been:

  1. We only use the public source (currently the V1.10.2 tag) from GitHub. These sources are unaltered locally, and built with the project makefile. If we find a bug or need a feature these changes are returned to libcli for official inclusion.
  2. Our documentation honors the attribution requirement in the LGPL and include the text of the LGPL license as provided in the libcli source tree.
  3. We link dynamically, so our end users can use a different version they can simply replace the dynamic library.

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

2 participants