On Sun, Oct 11, 2009 at 3:21 AM, Zefram <zef...@fysh.org> wrote: >>17.02) Make the license field an arrayref rather than a scalar. >> > Could make the field a string expression, with the defined keywords as > atomic expressions, "|" and "&" operators for license combination, and > parens for precedence. A distro with some files Perl-licensed and some > pure-GPLed could then be expressed as "gpl & perl". "perl" itself is > defined as "gpl | artistic".
-1 License can never really be determined without actually reading the source. I don't want to see us create a mini-language to describe license combinations. As I said in the original comments -- I don't think anyone actually uses the "license" field in META today. Case examples anyone? Can we adopt a YAGNI principle on license? -- David
