At 7:53 PM +0400 5/29/12, Michael Klishin wrote:
>> Are the Ruby headers for 1.9.2-p320 installed on a standard worker box?
>> If so where are they located?
>What is a standard worker box? There are several types of them
> * Ruby
> * JVM + Erlang + Haskell
> * PHP + Perl + Python
> * nodejs
Right now I'm specifying the language as nodejs. However I use a great deal of Ruby in the build system. I'll probably change the language to Ruby/RVM 1.9.3-p194 and install the nodejs dependencies by hand soon.
Additionallly (though not tested yet in travis) the a application also includes a rails server in the './server' dir. In the Gemfile for the rails app the debugger gem is contained in the group :development group.
Perhaps I can do this for the top-level Gemfile also -- but the Ruby code there is not running in Rails and doesn't yet have the concept of different environments.
I added the 'debugger' gem to the top-level Gemfile because it's useful for any developer working on the project.
I can also take it out and have developers install the 'debugger' gem manually -- or figure out how to easily represent different environments to bundler.
My first approach (which certainly may not be the best) was to see if there is a way to get the existing top-level Gemfile working as is.
>For all of them, Rubies are provisioned using RVM and because so many native extensions install, headers are obviously available.
>Relying on a specific location is a bad idea.
I think the debugger needs access to headers that are only available in a source install.
>Using Ruby's config sounds
>like a better option. I still don't see why you would need ruby-debug in CI environment, given thatwe have been asking
>people to exclude it from installing for over half a year now.
Of course you are right when you say the is NO need for debugger to be installed on a CI box.
I just started using travis-ci and didn't see the warnings about not to install a debugger.