Justin Baker

@luislavena @wycats This is only happening with prepackaging `rake`. So even if you made it the default the problem would persist unless it was fixed during packaging. Installing/reinstalling `rake` or...

@luislavena Also the way to set the defaults in `operating_system.rb` (from the best that I can tell) is like this: ```ruby Gem::ConfigFile::OPERATING_SYSTEM_DEFAULTS.merge!({'gem' => '--env-shebang'}) ``` But any configuration in your...

This is the best solution I've seen yet to this problem. That being said I'm still a little skeptical of using anything that is in `extensions` because there's always going...

@drbrain @knu That's actually really good compromise. I would totally accept/merge that. Thank you for looking at it. :smile: @drbrain I do have a quick question about `extensions` though. Was...

@knu Alright, well if you find a solution that you like then I'll be glad to help you getting it running on RubyInstaller.

@knu Sorry, I meant in addition to this change. For this if could just change the location of the check so that we can fail to load the DevKit THEN...

Here's where the fun part starts. > A working Ruby installation (guess will recommend use latest so dogfooding applies) I think there's still a problem with `Program Files` redirection or...

@zzak Thanks for the offer again! I'm going to shift the conversation over to vertiginous/rdoc_chm#7, where I added some more context.

The test results between my local build system and a hypervised system seem to been different. I get a lot of additional errors on a VM than on my local...

> By "compile environment" (and "environment"), I suppose you mean "DevKit type" (or "flavor"); and Yes > By "universal default," I suppose you mean "a single DevKit type which succeeds...