Skip to content
This repository has been archived by the owner on Mar 26, 2023. It is now read-only.

Use Standard Rubygems + Bundler #378

Open
mmmries opened this issue Mar 20, 2015 · 0 comments
Open

Use Standard Rubygems + Bundler #378

mmmries opened this issue Mar 20, 2015 · 0 comments

Comments

@mmmries
Copy link
Contributor

mmmries commented Mar 20, 2015

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant