How are license keys of ExtUtils::MakeMaker and CPAN::Meta::Spec related?

kcott has asked for the wisdom of the Perl Monks concerning the following question:

I encountered an invalid license value (which I've redacted to XXX) when working with a legacy Makefile.PL which contained:

WriteMakefile(
    ...
    LICENSE          => 'XXX',
    ...
);
[download]

When I ran perl Makefile.PL, I got:

Invalid LICENSE value 'XXX'
[download]

I looked in the LICENSE section of ExtUtils::MakeMaker. That didn't provide any direct help but had a link to CPAN::Meta::Spec for more information. Looking in the license section of that document, I found examples showing values as arrayrefs, followed by a list of the only valid values. I changed Makefile.PL to:

    LICENSE          => ['restricted'],
[download]

Running perl Makefile.PL again, I now get:

WARNING: LICENSE takes a string/number not a ARRAY reference.
[download]

I thought it was a bit of a long shot but, as CPAN::Meta::Spec had consistently used lowercase license, I tried:

    license          => ['restricted'],
[download]

but that only got me

WARNING: license is not a known parameter.
[download]

Anyway, I found that

    LICENSE          => 'restricted',
[download]

generated no warning or error messages. I had several legacy modules to deal with and subsequently came across one with

    LICENSE          => 'unrestricted',
[download]

which also worked without any issues.

So, that solved my immediate problem.

However, I'm still a little baffled by the apparent contradiction of a single string versus an array of strings; especially as CPAN::Meta::Spec has in its DESCRIPTION:

"Distribution building tools like ... ExtUtils::MakeMaker ... should create a metadata file in accordance with this specification ..."

I don't see how ExtUtils::MakeMaker, which only allows a single license value, could create the multiple license values as described in CPAN::Meta::Spec.

I get the feeling that one or both of these modules has problematic documentation, or that I'm missing some other information which glues these two together.

Any enlightenment would be greatly appreciated.

— Ken

Comment on How are license keys of ExtUtils::MakeMaker and CPAN::Meta::Spec related? Select or Download Code

Replies are listed 'Best First'.
Re: How are license keys of ExtUtils::MakeMaker and CPAN::Meta::Spec related? by Anonymous Monk on Mar 13, 2020 at 07:12 UTC
If you look at the files generated The eumm generated MYMETA.json/META.json use meta-spec 2.0 http://search.cpan.org/perldoc?CPAN::Meta::Spec where license is an array while the MYMETA.yml/META.yml uses http://module-build.sourceforge.net/META-spec-v1.4.html#license where license is a string I don't see how ExtUtils::MakeMaker, which only allows a single license value, could create the multiple license values as described in CPAN::Meta::Spec. Its possible using https://perldoc.perl.org/5.30.0/ExtUtils/MakeMaker.html#META_ADD/META_MERGE The yml files end up with a string, the json files end up with an array `LICENSE Available in version 6.31 and above. The licensing terms of your distribution. Generally it's "perl_5" for +the same license as Perl itself. See CPAN::Meta::Spec for the list of options. Defaults to "unknown".` [download] This means it takes a string	[reply] [d/l]
Re^2: How are license keys of ExtUtils::MakeMaker and CPAN::Meta::Spec related? by kcott (Archbishop) on Mar 13, 2020 at 14:04 UTC
++ Many thanks for that information. I think `META_ADD` and `META_MERGE` fill the gaps to which I alluded with: "... I'm missing some other information which glues these two together." — Ken	[reply] [d/l] [select]


more useful options
	PerlMonks