fix(upstart): Install inotify-tools if using upstart

[jayofdoom]

• This should fix issue upstart init config depends on inotifywait which isn't installed #41 I filed

My primary concern is that it appears inotify-tools is only available in RHEL via EPEL? Given they don't use upstart though, is this an issue? I don't really run any redhat-based OSes so it's a bit hard for me to tell.

[bflad]

Great catch. Surprised I haven't run into this during testing. Anything special about your Ubuntu setup? :)

While you could theoretically use Upstart init_type on RHEL family machines, I don't think we need to necessarily support it since CentOS/RHEL 6 is primarily sysv (by default) and 7 will be primarily systemd (by default assuming they're following Fedora's footsteps - I haven't messed around with the 7 Beta yet). I guess we'll see if anyone really wants it; it wouldn't be too hard to add.

[jayofdoom]

@bflad While I have this running on real machines, most of the issues I'm filing is against a local vagrant VM based on Ubuntu Precise w/the Saucy kernel installed. Basically all it's doing is installing omnibus chef, and running a small recipe that loads all these. I intend on using chef-docker to manage all this in production as well, hence why I've been finding+fixing every little thing I see in dev to lessen impact when I take this to my production environment.