Re^2: mbtiny and Minilla workflow - one rev behind in CPAN

I'm using mbtiny to generate these files: Build.PL, MANIFEST, META.json, and META.yml. If Minilla will handle those then I could drop mbtiny. Maybe I'm causing more problems with including META.yml since it seems to be just for legacy tools. I'll see if I can figure that out.

Comment on Re^2: mbtiny and Minilla workflow - one rev behind in CPAN

Replies are listed 'Best First'.
Re^3: mbtiny and Minilla workflow - one rev behind in CPAN by Arunbear (Prior) on Feb 08, 2021 at 18:20 UTC
Minilla did generate all of those for my modules. Build.PL and META.json were generated by "minil new", and the other two by "minil release".	[reply]
Re^4: mbtiny and Minilla workflow - one rev behind in CPAN by Lotus1 (Vicar) on Feb 12, 2021 at 14:23 UTC
What OS are you using? I'm using Windows which seems to be the root of this problem. It turns out that the META.json file that Minilla created has backslashes in the module path. CPAN won't index it with backslashes in the path. roboticus pointed out the possibility of this being a problem but I didn't follow up since the first release worked eventually. Last night I created a new distribution with Minilla and manually fixed the path before manually uploading to CPAN. That worked.	[reply]
Re^5: mbtiny and Minilla workflow - one rev behind in CPAN by Arunbear (Prior) on Feb 13, 2021 at 13:49 UTC
I use MacOs. After some digging, I found that for building the META.json, Minilla uses Module::Metadata which has this open bug, so it unfortunately doesn't do the right thing on Windows.	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.