Raku Land



Actions Status


App::Mi6 - minimal authoring tool for Raku


$ mi6 new Foo::Bar # create Foo-Bar distribution
$ mi6 build        # build the distribution and re-generate README.md/META6.json
$ mi6 test         # run tests
$ mi6 release      # release your distribution to CPAN


First make sure you have rakudo v2019.11 or later. If not, install rakudo from https://rakudo.org/downloads.


$ zef install App::Mi6


App::Mi6 is a minimal authoring tool for Raku. Features are:


Can I customize mi6 behavior?

Yes. Use dist.ini:

; dist.ini
name = Your-Module-Name

; if you want to disable generating README.md from main module's pod, then:
; enable = false
; if you want to change a file that generates README.md, then:
; filename = lib/Your/Tutorial.pod

; if you want to prune files when packaging, then
; filename = utils/tool.pl
; you can use Raku regular expressions
; match = ^ 'xt/'

; if you do not want to list some files in META6.json as "provides", then
; filename = lib/Should/Not/List/Provides.rakumod

; if you want to add badges to README.md, then
; provider = travis-ci.org
; provider = travis-ci.com
; provider = appveyor
; provider = github-actions/name

How can I manage depends, build-depends, test-depends?

Write them to META6.json directly :).

Where is the spec of META6.json?


See also The Meta spec, Distribution, and CompUnit::Repository explained-ish by ugexe.

What is the format of the .pause file?

Mi6 uses the .pause file in your home directory to determine the username. This is a flat text file, designed to be compatible with the .pause file used by the Perl5 cpan-upload module (https://metacpan.org/pod/cpan-upload). Note that this file only needs to contain the "user" and "password" directives. Unknown directives are ignored.

An example file could consist of only two lines:

user your_pause_username
password your_pause_password

Replace your_pause_username with your PAUSE username, and replace your_pause_password with your PAUSE password.

This file can also be encrypted with GPG if you do not want to leave your PAUSE credentials in plain text.

What existing files are modified by mi6?

After the initial mi6 creation step, the following files are changed by mi6 during each build or release operation:

How is the version number specified?

When you are ready to release a module and enter at the CLI mi6 release, you will get a response presenting a proposed version number which you can either accept or enter a new one (which must be greater than the one offered by default).

During the release, mi6 updates the files mentioned above with the selected version number.

What is the required format of the Changes file before a release?

Ensure your Changes file looks like something like this before you start a release operation

    - Change entry line 1
    - Change entry line 2
    - Change entry line 3








Shoichi Kaji skaji@cpan.org


Copyright 2015 Shoichi Kaji

This library is free software; you can redistribute it and/or modify it under the Artistic License 2.0.