-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
What is the actual license? #48
Comments
README file is correct. What exactly do you expect from me? |
I shouldn't have opened an issue on a Friday, everybody knows that :) So yeah, I was under the impression that the " or later" part should have been part of the terms and conditions in the LICENCE file itself, but does not look like it. It's confusing to have a license file that applies both to GPL-2 AND GPL-2-or-later and the difference is to be made in source code, but that's not a project issue here. Sorry for the noise, will think twice about opening issues again :) Have a nice day! |
LICENSE file contains GPL-2 license.
README says GPL-2+.
From the comment at the top of source code files, I think it should be GPL-2+.
Desktop distros don't have a consensus:
https://archlinux.pkgs.org/rolling/archlinux-community-aarch64/pcsc-tools-1.5.7-1-aarch64.pkg.tar.xz.html (GPL)
https://centos.pkgs.org/8/epel-x86_64/pcsc-tools-1.5.3-3.el8.x86_64.rpm.html (GPL-2+)
https://freebsd.pkgs.org/13/freebsd-amd64/pcsc-tools-1.5.7.txz.html (GPL-2)
https://opensuse.pkgs.org/tumbleweed/opensuse-oss-aarch64/pcsc-tools-1.5.7-1.5.aarch64.rpm.html (GPL-2+ AND GPL-3+)
I don't know where openSUSE got the idea that some code is GPL-3+.
Can we settle this once and for all and have consistency across files :)?
Thanks!
The text was updated successfully, but these errors were encountered: