On 09/01/2009 09:42 AM, Kevin Kofler wrote: > Hi, > > this has recently come up in a discussion about the License tags of gcc and > mingw32-gcc. The guidelines are very clear here: > > https://fedoraproject.org/wiki/Packaging:LicensingGuidelines#Multiple_Licensing_Scenarios > >> If your package contains files which are under multiple, distinct, and >> independent licenses, then the spec must reflect this by using "and" as a >> separator. > > There's even an example to clarify this: > >> License: Python and LGPLv2+ and BSD > > This is also reflected in the FAQ: > https://fedoraproject.org/wiki/Licensing:FAQ#How_should_I_handle_multiple_licensing_situations.3F > > It shall be noted that commas are also not allowed in dual-licensing > scenarios, where "or" is the required separator. > > Thus the following License tag is NOT valid: >> License: GPLv3+, GPLv3+ with exceptions and GPLv2+ with exceptions > > It should be fixed to read: > License: GPLv3+ and GPLv3+ with exceptions and GPLv2+ with exceptions > > The goal here is not to write stylistically nice English, but to write 100% > unambiguous, automatically parsable text. The rpmlint tool is correct in > complaining about this. Yes... this is all correct. Any package that is using commas in the license field should have a bug opened against it. ~spot -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
