Dependency Resolution with Standard Libraries
0 likes•815 views
The document discusses the roadmap for RubyGems and Bundler integration with Ruby 3.0. Key points include: 1) RubyGems 3.1 and Bundler 2.1 were recently released with improvements like lazily loading default gems. 2) Future versions will continue merging the projects, with RubyGems 3.2/Bundler 2.2 integrating into Ruby 2.8. 3) Ruby 3.0 will focus on "gemifying" standard libraries by extracting them to default gems, though some may be excluded. 4) This will require addressing issues around dependency and version resolution for the new default gems.
Dependency Resolution with Standard Libraries
- 1. The roadmap of RubyGems for Ruby 3.0 Hiroshi SHIBATA / GMO Pepabo, Inc. 2020.09.05 RubyKaigi takeout 2020 Dependency Resolution with Standard Libraries
- 2. Hiroshi SHIBATA @hsbt https://www.hsbt.org Executive Officer VP of Engineering Technical Director at GMO Pepabo, Inc. @pepabo
- 3. Agenda •The introduction for RubyGems 3.1 and Bundler 2.1 •Recent Update for RubyGems 3.2 and Bundler 2.2 •The feature plan and Roadmap for Ruby 3.0
- 4. The introduction for RubyGems 3.1 and Bundler 2.1
- 5. What’s new in RubyGems 3.1? RubyGems 3.1 has been released at 16 Dec, 2019 https://blog.rubygems.org/2019/12/16/3.1.0-released.html The key features: • Add the multi-factor authentication for `gem yank` command • Cleanup the compatibility code of Ruby 1.8 and 1.9 • Bundle Bundler 2.1
- 6. Lazily load the default gems We make these library to lazily load in RubyGems. •open3 •uri It did prevent that you specify the several versions of the default gems.
- 7. What’s new in Bundler 2.1? Bundler 2.1 has been released at 15 Dec, 2019. https://github.com/bundler/bundler/releases/tag/v2.1.4 The key features: • There is no incompatible feature from Bundler 2.0.x(maybe…) • Cleanup the compatibility code of Ruby 1.8 and 1.9 • Tuned on the deprecation warnings for Bundler 3
- 8. Tuned on the deprecation warnings for v3 •`bundle console` •`bundle viz` •`bundle inject` Bundler::SharedHelpers.major_deprecation 2 •Bundler.environment → Bundler.load •Bundler.clean_{env,exec} → Bundler.unbundled_{env,exec} •Bundler.with_clean_env → Bundler.with_unbundled_env
- 9. Recent Update for RubyGems 3.2 and Bundler 2.2
- 10. RubyGems/Bundler integration We merged bundler org into rubygems org. The repository, team, maintainers was merged.
- 11. RubyGems/Bundler integration •We also merged bundler repo into rubygems repo as monorepo. •The commits, CI, mainainers documents was merged Before After
- 12. Recent Works We still use separated release workflow about RubyGems and Bundler. We try to merge these toolchains at first. •Rubocop Rule 🤖 •Changelog(or History.txt) 📚
- 13. Bump up RubyGems/Bundler We will merge into RubyGems 3.2 and Bundler 2.2 into Ruby 2.8.0-dev. After that, RubyGems 4.0 will be merge Ruby 3. Ruby Bundler RubyGems 2.7.0 3.0 3.1 2.0 3.0 2.1 3.2 4.0 ? 2.2
- 14. Gemification for Ruby 3
- 15. Standard Libraries Default Gems Bundled Gems Pure Ruby 22 36 6 C extensions 12 17 0 This matrix shows number of standard libraries and their classifications in Ruby 2.7. Gemification for Ruby 2.7
- 16. Gemification for Ruby 2.8/3.0 Notable Changes •`net-telnet` was removed from the bundled gems •`rexml` and `rss` promoted the bundled gems from the default gems. I’ll work to publish the all of stdlib to the default gems •Except to use `internal.h` or `internal/*.h` and depends on Ruby version •Ex. mkmf.rb, objspace, pty, ripper, socket, coverage
- 17. Gamification on Ruby 3.0(TBD) We will extract the standard libraries to the default gems. Abbrev Base64 DEBUGGER__ DRb ERB Find OpenURI OptionParser PP PrettyPrinter resolv-replace.rb Resolv Rinda SecureRandom Set Shellwords Time TSort un.rb Digest IO(wait and nonblack) Monitor(Ruby 2.6 version) NKF Pathname Syslog Win32API WIN32OLE
- 18. Activation issues about the default gems You couldn’t use the specified version of default gems like json when RubyGems/Bundler activated them. When RubyGems uses json-2.1.0, You couldn’t use json 1.8.x. Because ruby gems and rubygems.org never uses JSON format. Because Bundler still use the original implementation for YAMLSerializer.
- 19. What should we do? 1. Don’t use the default gems in `Bundler.setup`, `Kernel#require` and etc. → 😆 2. Vendoring approach when RubyGems uses only pure ruby libraries like URI. → 😩 3. Rewrite pure ruby code without the default gems. → 😩
- 20. Rewrite the default gems to Ruby code We should rewrite the URI and FileUtils without the default gems. Ex. Bundler uses FileUtils with the following methods. • FileUtils.mkdir_p • FileUtils.cp_r • FileUtils.rm_rf • FileUtils.touch
- 21. Gamification on Ruby 3.0(TBD) We should keep the following gems with irb and rubygems. We will extract the default gems to the bundled gems without them. did_you_mean fileutils forwardable io/console reline readline-ext delegate pathname set tsort pathname And also keep the following gems for `bundle exec`. tempfile timeout tmpdir
- 22. The major problem for the bundled gems If you use Bundler, you need to add the bundled gems into your Gemfile. source "https://rubygems.org" git_source(:github) {|repo_name| "https://github.com/#{repo_name}" } gem "english" gem “uri” gem “openssl” … I need to consider to transition and migration plan for this. But I have no idea yet. Maybe, I will add the some mechanism to Bundler internal to care about this.
- 23. Conclusion
- 24. Conclusion •Finally, We will start to merge RubyGems and Bundler for unifying the one command. •I’m working to extract stdlib to the default gems in Ruby3 •We should remove the current dependency from rubygems and bundler. Let’s join to #rubygems in ruby-jp slack