Install of rake and then gem that is built using rake in same "bundle install" fails

[crowbot]

Installing the bundle shown in this gist produces the error shown.

https://gist.github.com/3775908

The xapian-full-alaveteli gem is built using rake, but bundler is trying to access the rake executable in the temporary location where the rake gem was built - and by this point it has been copied to /usr/local/bin/rake, so is no longer there.

[indirect]

As you can see from the Bundler output, rake is always installed first, specifically because many gems require rake in order to build themselves. This is the first gem to have this problem, and many other gems that require rake to build work just fine, so I'm inclined to think this is a bug in the build process for the xapian-full-alaveteli gem. Do you have reason to think this is a bug in Bundler?

[crowbot]

Hi, thanks for the quick reply. I've been trying to figure out if it's a bug in bundler, rubygems, or the xapian-full-alaveteli gem - I came to the initial conclusion that I didn't think it could be the xapian-full-alaveteli gem because there doesn't seem to be anything in it's rakefile [1] or gemspec [2] that could be setting the rake executable path. I'm fairly new to bundler - is there anything obviously unusual looking in those files that might cause a problem with bundler?

[1] https://github.com/sebbacon/xapian-full/blob/master/Rakefile

[2] https://github.com/sebbacon/xapian-full/blob/master/xapian-full.gemspec

[indirect]

Well, the gemspec certainly seems to be non-standard in the sense that it contains the line s.extensions = ["Rakefile"]. According to the gemspec specification, that array is supposed to contain "extconf.rb-style files" that will be "executed directly". Rakefiles aren't designed to be executed, they're designed to be loaded by the rake command. So this gem seems to be doing something non-standard, yes.

[crowbot]

OK, great - I'll follow that up. Thanks for your help!

[crowbot]

Having gone into this further, I see that Rakefiles are included in the list of files that can be given as extensions in the Rubygems documentation, so I believe there's nothing non-standard going on with the gemspec itself. I've found the bug in bundler that's causing the issue and submitted a pull request with a spec and fix. #2187

[indirect]

Closing this since the pull has been merged.

[indirect]

Uh. I mean opening, apparently. Closing now. :)