Removed support 'freezing daemon-kit into vendor/'

[kennethkalmer]

This is such a relic of the pre-bundler days. We can now simply have folks update their Gemfile to point to our master branch directly, no need to special 'vendor/daemon-kit' magic.

[ ] - Cleanup boot.rb
[ ] - Make sure it can be upgraded cleanly with rake daemon_kit:upgrade
[x] - Document in upgrading.txt
[ ] - Document in post-install, blog post etc

This might just break 0.2.x upgrades

[coveralls]

Coverage decreased (-2.53%) when pulling 9f89374 on living-on-the-edge into ef4573a on master.

[marcbowes]

[kennethkalmer]

@marcbowes 👍

Just need to tweak the daemon_kit:upgrade task to use the app generator, but invoke selectively.

[coveralls]

Coverage decreased (-2.35%) when pulling 8ec558e on living-on-the-edge into ef4573a on master.

[kennethkalmer]

@marcbowes eyes please, I'm not too happy with a stub project added in 286a8e5, but is was needed to the scenario added in 17b10d8

I think this branch is good to be merged!

[kennethkalmer]

We can always refine the tests after 0.3 drops, just want the upgrade process to be smooth.

[marcbowes]

lgtm

[kennethkalmer]

👍

Let me just fix the failures caused by rspec trying to load the fixtures directory and subsequently failing to boot the daemon :/

[coveralls]

Coverage decreased (-1.79%) when pulling 2d8eaed on living-on-the-edge into ef4573a on master.