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
{{ message }}
This repository has been archived by the owner on Mar 26, 2023. It is now read-only.
What do people think of getting rid of our custom rubygems + bundler implementation? There is a standard mechanism now for getting a platform-specific version of a gem.
A lot of work has gone into bundler and rubygems that don't work under maglev (ie. having a path in a gemfile and using bundle exec can mess up load paths). Rather than finding and fixing all of the inconsistencies I wonder if it would be better to rely on the existing implementations and work with the popular projects to release version of their gems specific to maglev where needed.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What do people think of getting rid of our custom rubygems + bundler implementation? There is a standard mechanism now for getting a platform-specific version of a gem.
A lot of work has gone into bundler and rubygems that don't work under maglev (ie. having a path in a gemfile and using bundle exec can mess up load paths). Rather than finding and fixing all of the inconsistencies I wonder if it would be better to rely on the existing implementations and work with the popular projects to release version of their gems specific to maglev where needed.
The text was updated successfully, but these errors were encountered: