Do things with Perl 6 [META files](
Perl6 Makefile
Latest commit 607f128 Jan 27, 2017 @jonathanstowe committed on GitHub Merge pull request #3 from zoffixznet/patch-1
Fix incorrect version in SYNOPSIS


Build Status

Do things with Perl 6 META files


The below will generate the for this module.

use META6;

my $m =   name        => 'META6',
                     description => 'Work with Perl 6 META files',
                     version     =>'0.0.1'),
                     perl-version   =>'6.*'),
                     depends     => <JSON::Class>,
                     test-depends   => <Test>,
                     tags        => <devel meta utils>,
                     authors     => ['Jonathan Stowe <>'],
                     auth        => 'github:jonathanstowe',
                     source-url  => 'git://',
                     support     =>
                        source => 'git://'
                     provides => {
                        META6 => 'lib/',
                     license     => 'Artistic',
                     production  => False,


print $;

my $m ='./META6.json');
$m<version description> = v0.0.2, 'Work with Perl 6 META files even better';
spurt('./META6.json', $;


This provides a representation of the Perl 6 META files specification - the META file data can be read, created , parsed and written in a manner that is conformant with the specification.

Where they are known about it also makes allowance for "customary" usage in existing software (such as installers and so forth.)

The intent of this is allow the generation and testing of META files for module authors, so it can provide meta-information whether the attributes are mandatory as per the spec and where known the places that "customary" attributes are used,


Assuming you have a working Rakudo Perl 6 installation you should be able to install this with panda :

# From the source directory

panda install .

# Remote installation

panda install META6

This should work equally well with zef but I have not tested it.


Suggestions/patches are welcomed via github at

I'm particulary interested in knowing about "customary" (i.e. non-spec) fields that are being used in the wild and in what software so I can add them if necessary.


Please see the LICENCE file in the distribution

© Jonathan Stowe 2015, 2016, 2017