rbenv/ruby-build

A tool to download, compile, and install Ruby on Unix-like systems.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 24 minutes ago
Added to GitGenius on September 17th, 2026
Created on August 2nd, 2011
Open Issues & Pull Requests: 4 (+0)
GitHub issues: Enabled
Number of forks: 807
Total Stargazers: 3,975 (+0)
Total Subscribers: 96 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 15.6 hours
Mean response time: 3.9 days
90th percentile: 8.5 days
Tracked items: 41

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 2
Closed in 7 days: 1
Avg open age: 532 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 2
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (27)
  • enhancement (3)

Most active issues this week

Detailed Description

ruby-build is a command-line tool that downloads, compiles, and installs Ruby from source on Unix-like systems.

The tool automates the process of obtaining Ruby source code, extracting it, running configure and make install, and verifying the result. It handles additional complexity by discovering and linking to system libraries like OpenSSL, libyaml, and readline, and can compile OpenSSL itself if needed. The tool works as a standalone program or as a plugin for rbenv, providing the rbenv install command.

ruby-build is suitable for developers who need to install multiple Ruby versions or manage Ruby installations across Unix-like systems. It supports CRuby, JRuby, mruby, PicoRuby, and TruffleRuby implementations. One important consideration is that ruby-build bundles definition files for each Ruby version rather than querying remote resources, so you must upgrade the tool itself to install newly released Ruby versions. The README identifies ruby-install as an alternative for users who prefer a tool that always consults remote resources for the latest version list without requiring tool upgrades.

Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker centers on bug reports and enhancement requests.