What do these RubyInstaller 2.4 components do?

The components are defined here. The single options do:

  1. Download, verify and run the MSYS2-installer. This installs the base MSYS2 environment (bash, pacman, tar, etc.) without development packages.
  2. Download the pacman repository inventory. This retrieves version information about all available MSYS2+MINGW packages.
  3. Download and install the development packages, which are typically required to compile ruby C extensions.

You should usually just press enter and execute all three options. And if something fails, you can restart the MSYS2 installation anytime later per ridk install.

My aim is to add some more component install options in the future. For instance to install bundler or rails or some other popular gems or extensions subsequent to the base ruby installation.

You don’t need to install the previous DevKit. MSYS2 replaces the DevKit starting with RubyInstaller-2.4.

Since MSYS2 has much more packages available then the old DevKit, it also makes installations of many source gems possible. While previously any dependent libraries needed to be shipped as source tar or as “fat binary gem” (like nokogiri), now dependent native libraries can easily installed per pacman, similar to apt-get on Debian/Ubuntu. This is a big advantage of MSYS2 compared to the DevKit. The other advantage is that the programs and libraries are more up-to-date and actively maintained.

Leave a Comment