On Tue May 26 15:57:26 2015, ETHER wrote:
Show quoted text> I'm not sure if you're doing this in your bundle itself, or through
> some other tool - apologies if this is the wrong queue.
>
> I've noticed that many of your distributions contain an auto-generated
> dist.ini, with reference to iller.yaml -- what is the tool that reads
> iller.yaml? I cannot find it. It would be extremely helpful to
> document this tool somewhere in each distribution where it is used
> (e.g. see my generated CONTRIBUTING document that is added to each of
> my releases), as a guide to contributors.
>
> I found
https://github.com/Csson/p5-Dist-Iller, but it's marked
> deprecated, and it's already gone from the cpan. Have you switched to
> something else?
The deprecated Dist::Iller was a first poor attempt. I have pushed the current version to github (
https://github.com/Csson/p5-Dist-Iller).
A bit of background: When I first started using Dist::Zilla and Pod::Weaver I spent many hours trying to figure out how it worked. I realized that, for me, a big problem was how plugin bundles are created. So instead, before dzil runs, I generate dist.ini and weaver.ini from three files:
Two files form the equivalent of plugin bundles:
https://github.com/Csson/p5-Dist-Iller-Config-Author-CSSON/blob/master/lib/Dist/Iller/Config/Author/CSSON.pm
https://github.com/Csson/p5-Dist-Iller-Config-Author-CSSON/blob/master/share/author-csson.yaml
And one file is the distribution configuration:
https://metacpan.org/source/CSSON/Mojolicious-Plugin-DbicSchemaViewer-0.0101/iller.yaml
That said, a goal with this solution is of course that it is fully Dist::Zilla/Pod::Weaver compatible, and I have no problem with pull requests to the generated files. Since I use a non-standard tool it's on me to incorporate such changes upstream.
But I should probably deprecate my plugin bundles..
I have changed my defaults to [MakeMaker] and [Git::Contributors]. Thanks for the heads up!
