installation with ruby buildpack causes build

[Drew Stokes]

hey guys. i've got a deployment pipeline involving an ubuntu 14.04 build server that builds and tarballs a rails application using the heroku ruby buildpack. gems are installed with the nokogiri system library env (https://github.com/heroku/heroku-buildpack-ruby/blob/8ea565367f7efc5a5df02ee4b8a5a2aea7ebeeb9/lib/language_pack/ruby.rb#L531) and everything seems to work until the tarball is extracted on another trusty machine. at that point, loading a rails console causes gem to rebuild nokogiri with the bundled libraries. am i missing something?

[Mike Dalessio]

Hi Drew,

I don't think this is a nokogiri-specific issue. Have you reached out to the Heroku Buildpack team?

On Jan 9, 2015 10:56 PM, "Drew Stokes" <drew....@fullscreen.net> wrote:

hey guys. i've got a deployment pipeline involving an ubuntu 14.04 build server that builds and tarballs a rails application using the heroku ruby buildpack. gems are installed with the nokogiri system library env (https://github.com/heroku/heroku-buildpack-ruby/blob/8ea565367f7efc5a5df02ee4b8a5a2aea7ebeeb9/lib/language_pack/ruby.rb#L531) and everything seems to work until the tarball is extracted on another trusty machine. at that point, loading a rails console causes gem to rebuild nokogiri with the bundled libraries. am i missing something?

--
You received this message because you are subscribed to the Google Groups "nokogiri-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nokogiri-tal...@googlegroups.com.
To post to this group, send email to nokogi...@googlegroups.com.
Visit this group at http://groups.google.com/group/nokogiri-talk.
For more options, visit https://groups.google.com/d/optout.