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

licensing #287

Open
ghost opened this issue Jul 2, 2024 · 1 comment
Open

licensing #287

ghost opened this issue Jul 2, 2024 · 1 comment

Comments

@ghost
Copy link

ghost commented Jul 2, 2024

Hi.

Thanks for the great package.

I am wondering whether I can use it in a commercial closed source project.

The R code I am developing will be distributed to companies in a byte-compiled package against a license fee.

I understand that developing and distributing closed-source packages is in principle possible but one has to check the licensing of packages used in the project(e.g. ok with MIT, not ok with GPL3 etc).

Looking at your license ......... it says nothing except that you own the copyright. Can you please clarify your position on using R6 in the above described commercial closed-source context.

Thanks

@wch
Copy link
Member

wch commented Jul 4, 2024

R6 is MIT licensed. This is set in a line in the DESCRIPTION file:

R6/DESCRIPTION

Line 14 in 5078678

License: MIT + file LICENSE

The reason it's done this way instead of with a LICENSE file is because CRAN wants it that way -- for some reason they do not allow standard LICENSE files to be part of the package.

More information about it here: https://r-pkgs.org/license.html#key-files

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