Consider making hard runit dependency optional

[michaelklishin]

We are evaluating perl-chef for first-class Perl support on http://travis-ci.org per @leto's recommendation. One thing I've hit immediately after cloning the repository is runit cookbook dependency. We do not use runit for Travis CI and I am yet to find how runit is used by perl-chef but it sounds like a non-essential dependency.

I can remove it for our version of the cookbook but maybe it is something that can be made optional (using a separate recipe or a condition attribute, for example).

[dagolden]

It can probably be made optional or split out. I used it for deploying a perl app as a service. That could possibly be a separate cookbook, 'perl_service' or 'perl_app' that itself depends on perlbrew.

I'm very happy to hear that you're evaluating it, but please do keep in mind that I'm at the 0.001 stage where I'm trying to figured out what will work best to make Perl and chef play nice together.

[michaelklishin]

@dagolden no problem. We are not new to modifying cookbooks to our needs. Maybe this is the best way to go for us. We will let you know if we find any points of improvement that are worth contributing back.