--- Comment #16 from Andy Mender <andymenderunix(a)gmail.com> ---
1. How should I check whether a license can have "GPLx with
exception"? It is listed in gdb package but I didn't see any license listed in
licensecheck.txt have such short name in the license guide.
I think you need to have a look at specific files listed in licensecheck.txt
and see whether the license header in them contains clauses which could be
considered exceptions from the general text of a particular GPL license. The
doc you mentioned earlier
gives examples of licenses which are GPL-like, but contain such clauses (for
instance, covering font embedding).
2. If license like "NTP" is not listed in the license
guide, can it simply be listed as "NTP"?
No, licenses which are not listed in the license guide need to go through
Fedora Legal (legal(a)lists.fedoraproject.org) for verification. NTP is actually
a misnomer for one of the MIT licenses:
When you compare the text of the NTP license to one of the "old style" variants
of the MIT license, it's exactly the same. I thought it was supposed to be
added to the license matrix in the license guide, but wasn't yet it seems.
3. What does "XXX GPL" mean(e.g. ISC License GPL)? How does
it related with GPL and the license itself? And how should I specify them in License
This I don't know, since ISC and GPL are different licenses. Have a look at the
file with the license header and compare to both the ISC license and the GPL3
license to see which one's more likely. If it's absolutely unclear, run it
through Fedora Legal.
I think your package should also contain the "Boost" license tag, even though
the original "gdb" package doesn't mention it.
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component