3 step instruction in README does not work due to missing rake dependency in Gemfile about octopress HOT 8 CLOSED

Works for me, what version of Bundler are you having this problem with? The solution you got from wycats (bundling rake and using "bundle exec rake") will work, but it shouldn't be necessary as long as the Bundler environment is being properly set up in the Rakefile. If not then we'd have to use "bundle exec rake" with our Rails 3 apps too, and I've never run into a case where I needed to do that.

from octopress.

Hm. Seems to be one of the differences of 0.9 vs. 1.0.

I could construct an edgecase where a blank ruby install, combined with the --deployment flag would make it neccessary to call rake via bundle exec. Exactly what the chances are that something like that happens - Well, beats me.

Still, rake is, I think, a valid dependency. I'll rollback the doc change, though.

from octopress.

I agree, rake is a valid dependency.. but even though there might be a few edge cases, in general I don't think "bundle exec rake" should be needed if the Bundler environment is set up in the Rakefile. I can't speak for carlhuda or wycats (or any of the other Bundler developers), but personally I think if the only way to fix this is "bundle exec rake" I'd call that a bug or regression in Bundler.

from octopress.

oops.. of course I meant carllerche and wycats :)

from octopress.

Sorry, just catching up here. What's the consensus here? Add rake as a dependency in the Gemfile?

from octopress.

I'd like to know why Bundler isn't handling the situation where the Bundler environment is set up in the Rakefile, but that isn't really your problem, if it bothers enough people I'm sure someone will report it as a Bundler bug. I don't see any problem with adding rake as a dependency in the Gemfile, it is a valid dependency and it allows people to use "bundle exec rake" if they need to.

from octopress.

Okay, so I've been chatting with Yehuda on this (we happen to be on the same conference right now), so I hope to have fully understood now how this works.

Bundler 1.0 IS actually handling this normally - 0.9 doesn't - but then again, that's probably irrelevant (although that's the current "stable" version, at least for a few days).

As I said, I am able to construct an edge case where a simple rake won't work (simply, because there isn't a rake binary in the PATH) and subsequently a bundle exec rake would fix things - if rake is added as a dep.

I'd vote for adding rake as a dep, but seriously basically this issue is largely my fault of trying to use octopress with an "old" bundler version. Duh.

from octopress.

Thanks for hound doggin' this for us. How about this? :)
http://github.com/imathis/octopress/commit/a9eb0781193f7eb5f3635d8124de6fc4e342a000

from octopress.