{"id":484,"date":"2010-06-24T20:27:22","date_gmt":"2010-06-24T19:27:22","guid":{"rendered":"http:\/\/www.streppone.it\/cosimo\/blog\/2010\/06\/distzilla-cpanhacker-do-you-use-it\/"},"modified":"2010-06-24T20:27:22","modified_gmt":"2010-06-24T19:27:22","slug":"distzilla-cpanhacker-do-you-use-it","status":"publish","type":"post","link":"https:\/\/www.streppone.it\/cosimo\/blog\/2010\/06\/distzilla-cpanhacker-do-you-use-it\/","title":{"rendered":"Dist::Zilla, cpanhacker, do you use it??!"},"content":{"rendered":"

Dist::Zilla, cpan hacker, do you use it?<\/a><\/p>\n

If not, you should. Full stop.<\/p>\n

So I've been reading about Dist::Zilla (dzil)<\/a> for a while now. The first articles didn't really convince me too much. Yes, it's a nice tool, but why would I want to use it? Ok, to save time. Right. But how do I use it the first time? I need a config file. Ok where do I get (a sane) one?<\/p>\n

Then I read a clear walk-through example of a Dist::Zilla config<\/a> by Dave Rolsky. So, the quick start route was clear. Copy\/paste the dist.ini<\/code> file and try it.<\/p>\n

Except, the file in that blog post contains so much stuff (read: additional plugins required) that is not practical to use as a first dist.ini<\/code> config.<\/p>\n

Basic premise<\/h3>\n

It's that you have to have a module\/class that you want to upload to the CPAN, and you want to save yourself all the "package-wrapping" activities that a CPAN distribution needs. That is were dzil shines.<\/p>\n

Start-using-Dist::Zilla-in-2-minutes guide<\/h3>\n

Good, you're on your way to spend countless hours less on maintaining your CPAN stuff.<\/p>\n