> % starperl Build.PL
> [...]
> Could not get valid metadata. Error is: Invalid metadata structure. Errors:
> License 'gpl2' is invalid (license) [Validation: 1.4]
> at /soft/mjc/classic/Perl/lib/perl5/5.18.2/Module/Build/Base.pm line 4571.
Hello,
It seems that this behaves differently in different Perl environments.
Sometimes "gpl" is interpreted as GPL version 1 (not what we want) so
"gpl2" is required, but other times "gpl" is treated generically and
"gpl2" is not recognised.
Here's what is written into the MYMETA file in each case:
Newly-built "starperl":
"gpl": http://opensource.org/licenses/gpl-license.php
"gpl2": error
"GPL_2": error
(however it can install the Astro::FITS::HdrTrans package from
CPAN, presumably because the META files are present)
EAO "local" Perl:
"gpl": http://www.gnu.org/licenses/old-licenses/gpl-1.0.txt
"gpl2": http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt
"GPL_2": http://www.gnu.org/licenses/old-licenses/gpl-2.0.txt
(this is the Perl installation I use to build
Astro::FITS::HdrTrans for CPAN, so "gpl2" seems to be what I need
to do that)
I think the difference is the presence of the Software::License module.
This can be installed as follows:
$ $STARLINK_DIR/Perl/bin/cpanm Software::License
Then with "starperl", "gpl2" is recognised:
$ starperl Build.PL
[...]
Created MYMETA.yml and MYMETA.json
Creating new 'Build' script for 'Astro-FITS-HdrTrans' version '1.58'
Best regards,
Graham
|