As per https://gitlab.com/libidn/libidn2/-/blob/master/COPYING?ref_type=heads https://gitlab.com/libidn/libidn2/-/blob/master/COPYING.unicode?ref_type=heads LICENSE should contain the aforementioned license. I cannot find the equivalent license in portage/licenses (NOT unicode). At least https://gitlab.com/libidn/libidn2/-/blob/master/src/idn2.c?ref_type=heads is GPL3+. So at the end LICENSE should be "||( LGPL-3+ GPL-2+) GPL-3+ *COPYING.unicode*" Reproducible: Always
The "terms of use" aren't part of the copyright license. What concerns us is the "EXHIBIT 1" starting at line 36. AFAICS that's "Unicode-DFS-2016", which we have. Disclaimer: IANAL, TINLA.
Well it says under https://gitlab.com/libidn/libidn2/-/blob/master/COPYING.unicode?ref_type=heads "This project is licensed under the Unicode Terms of Use." IANAL, so I err on the safe side for such things, since judical enforcability may also be a "common law vs civil law"-issue depending on where you reside.
The terms of use are part of what we have as licenses/unicode. Word by word comparison with COPYING.unicode shows some small differences, e.g. item numbers have been dropped. IMHO these differences are insignificant, but YMMV. Then again, the terms say that "Unicode shall have the right to modify this Agreement at any time by posting it to this site", so possibly the relevant text is the one that we find today at https://www.unicode.org/copyright.html. Thinking about it, this clause probably fails the "tentacles of evil" test (see https://wiki.gentoo.org/wiki/License_groups#When_is_a_license_a_free_software_license.3F), which would make the Unicode terms of use non-free.
GNU Emacs also has that license: https://git.savannah.gnu.org/cgit/emacs.git/tree/admin/unidata/copyright.html#n248 ... which gives me the opportunity to ask the FSF about it. Stay tuned. :)
https://lists.gnu.org/archive/html/emacs-devel/2023-08/msg00844.html "As you yourself say, correctly, these files contain data, not code, and the data is of the kind that hardly ever justifies copyright." Relevant case law seems to be (again, IANAL): https://en.wikipedia.org/wiki/Feist_Publications,_Inc.,_v._Rural_Telephone_Service_Co. Anyway, I'd suggest to update the ebuild to LICENSE="|| ( GPL-2+ LGPL-3+ ) GPL-3+ unicode" and to update licenses/unicode to the text from unicode.org. We can leave it to users to decide if they consider the Unicode data files copyrightable (or they can ask their lawyer about it).
Agreed. The unicode issue and if the the included data is copyrightable and thus the license enforceable may only be resolved in the context of your local legal system.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=22f4f885c4338c544d2e955a427281fffa64f896 commit 22f4f885c4338c544d2e955a427281fffa64f896 Author: Andreas K. Hüttel <dilfridge@gentoo.org> AuthorDate: 2023-09-20 21:10:40 +0000 Commit: Andreas K. Hüttel <dilfridge@gentoo.org> CommitDate: 2023-09-20 21:10:40 +0000 net-dns/libidn2: update LICENSE Closes: https://bugs.gentoo.org/912408 Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> net-dns/libidn2/libidn2-2.3.4-r1.ebuild | 2 +- net-dns/libidn2/libidn2-2.3.4.ebuild | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) Additionally, it has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a9e4c2c074b821c3983277a8e3acb95aacdf9652 commit a9e4c2c074b821c3983277a8e3acb95aacdf9652 Author: Andreas K. Hüttel <dilfridge@gentoo.org> AuthorDate: 2023-09-20 21:09:01 +0000 Commit: Andreas K. Hüttel <dilfridge@gentoo.org> CommitDate: 2023-09-20 21:09:01 +0000 licenses: Update unicode license from website https://www.unicode.org/copyright.html Bug: https://bugs.gentoo.org/912408 Signed-off-by: Andreas K. Hüttel <dilfridge@gentoo.org> licenses/unicode | 301 ++++++++++++++++++++++++------------------------------- 1 file changed, 132 insertions(+), 169 deletions(-)
