Adam Kennedy wrote:
There's a few classes of checks we can do.

If the package has a META.yml, it should have a license field. There are about a dozen legitimate values.

license 'restrictive'

The is an absolute positive match for a disallowed license.

A check covering the above case could safely be added immediately.

Beyond that you have three additional cases...

- The license value exists but is not a known type

- There is no license value in the META.yml

- There is no META.yml

There is a snapshot of how the license field in META.yml is used at:

  <http://thepierianspring.org/perl/meta>

    1 GPL             # wrong case
    4 GPL version 2   # invalid value
    3 GPLv2           # invalid value
    3 INVALID         # These have a url as a value
    1 LGPL            # wrong case
 3619 NONE            # No license field
    1 Perl            # wrong case
   50 artistic
   26 bsd
   61 gpl
    6 lgpl
   10 open_source
 1497 perl
    2 restrictive
   26 unknown         # invalid value: literal 'unknown'
    3 unrestricted

There should probably be a gpl2 & gpl3. Do we care about case?

Randy.

Reply via email to