You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't want to ship rake or packager in my package, but I do want to isolate the gem versions referenced in my rakefile so that I can have a predictable build process. If I put rake in the Gemfile so that I can say bundle exec rake packager:pkg and not get gem activation errors when building my stable release when I have unstable versions on my system, then rake gets packaged too.
Workaround was to use rvm gemsets that match my bundled versions :(
The text was updated successfully, but these errors were encountered:
Packager uses bundler so I'm not sure how it could hate it. I must admit that I'm confused by exactly what your problem is and what you think it should do.
My point is that there needs to be a bundle that is used for running packager. And a DIFFERENT bundle that is used making the package -- otherwise I end up shipping code that doesn't need to be shipped (like rake, packager, rspec, etc)
I don't want to ship rake or packager in my package, but I do want to isolate the gem versions referenced in my rakefile so that I can have a predictable build process. If I put rake in the Gemfile so that I can say
bundle exec rake packager:pkg
and not get gem activation errors when building my stable release when I have unstable versions on my system, then rake gets packaged too.Workaround was to use rvm gemsets that match my bundled versions :(
The text was updated successfully, but these errors were encountered: