Hi,
"Is there an easier alternative to these two?"
I can't say whether it's easier, not having used your toolkit, but I am a big fan of Dist::Zilla. Yes it is intimidating at first glance and you'd have a steeep learning curve if trying to go from scratch with the doc (as I once did) ... but there's no need to with the many great examples of .ini files out there. My own now very stable one is based on David A Golden's. You're welcome to copy it as I did his.
With the ini file I've developed, my workflow for a new release is very painless and fast. I just have to commit the work and a Change note and run the program; versioning bumping, git tagging and pushing, etc all rolled in. The distribution ships with a standard Makefile.
I see a lot of threads about distro release/build woes, and most often folks eschew the D::Z option because of perceived diffculty. It's nothing but smooth sailing for me :-)
Hope this helps!
In reply to Re: mbtiny and Minilla workflow - one rev behind in CPAN
by 1nickt
in thread mbtiny and Minilla workflow - one rev behind in CPAN
by Lotus1
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |