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

GPL license is ambiguous #12

Open
merkys opened this issue Sep 20, 2021 · 3 comments
Open

GPL license is ambiguous #12

merkys opened this issue Sep 20, 2021 · 3 comments

Comments

@merkys
Copy link

merkys commented Sep 20, 2021

To date, there are three versions of GNU GPL license, each differing from the other. It would be great to see GPL version number in the license of the code to unambiguously know what are the permissions for (re)use.

@levitte
Copy link

levitte commented Jan 3, 2023

Not sure why you're talking about a GPL license, as it's not used here (as far as I can tell at least).

The license can be found here: https://github.com/dot-asm/cryptogams/blob/master/LICENSE

@merkys
Copy link
Author

merkys commented Jan 3, 2023

I mean the following lines of the same LICENSE file:

cryptogams/LICENSE

Lines 21 to 24 in 097e2c7

ALTERNATIVELY, provided that this notice is retained in full, this
product may be distributed under the terms of the GNU General Public
License (GPL), in which case the provisions of the GPL apply INSTEAD OF
those given above.

@noloader
Copy link

noloader commented Jan 3, 2023

I mean the following lines of the same LICENSE file...

I believe that clause is present because the Linux kernel uses some of Andy's routines. Andy had to supply a compatible license for the kernel.

In the context of the kernel, it will be GPL v2.0. Also see https://www.kernel.org/doc/html/v4.16/process/license-rules.html .

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

3 participants