You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
Hiroshi SHIBATA 7a3ed022d4
Merge pull request #6463 from rubygems/allow-config-install-extension-in-lib
20 hours ago
.bundle Use bundler to manage development dependencies 4 years ago
.devcontainer match devcontainer json indentation to project 4 months ago
.githooks fix pre-commit hook failing rubocop on non-ruby files 4 months ago
.github Bump the artifacts group with 2 updates 1 week ago
bin Make bin/rubocop resolve config relative to itself 2 months ago
bundler Merge pull request #7475 from rubygems/avoid-to-race 2 days ago
exe Rename bindir as exe 9 months ago
hide_lib_for_update Remove outdated upgrade instructions 3 years ago
lib Keep Gem.install_extension_in_lib for compatibility 22 hours ago
test re-order util methods 22 hours ago
tool lock with all platforms 2 weeks ago
.changelog.yml Rename `backport` labels 1 month ago
.codeclimate.yml Ignore test files for CodeClimate 2 years ago
.codespellignore Add codespell to GitHub actions 1 year ago
.codespellrc Ignore all vendored libraries from spellchecking 2 months ago
.git-blame-ignore-revs Add giant commit to .git-blame-ignore-revs 3 months ago
.gitattributes Revert part of the new `.gitattributes` files 4 years ago
.gitignore Add .ruby-version to .gitignore 1 month ago
.rubocop.yml Vendor uri gem in RubyGems 4 weeks ago
CHANGELOG.md Changelog for Rubygems version 3.5.6 2 weeks ago
CODE_OF_CONDUCT.md Merge CoC from bundler repo. 4 years ago
CONTRIBUTING.md Update command to test local gem command changes 8 months ago
LICENSE.txt Remove reference to missing LICENSE file 12 years ago
MAINTAINERS.txt Update MAINTAINERS.txt 4 years ago
MIT.txt Update MIT credits for near-identical bundler code 10 years ago
Manifest.txt Rename molinillo wrapper file to vendored_molinillo.rb 3 weeks ago
POLICIES.md Rename `backport` labels 1 month ago
README.md Update supported versions in README 2 months ago
Rakefile Refactor to list gemfiles 2 weeks ago
UPGRADING.md Use inline codeblock for sh commands 3 years ago
rubygems-update.gemspec Add metadata for rubygems.org 3 weeks ago
setup.rb Drop support for Ruby 2.6 and Ruby 2.7 in RubyGems 3 months ago

README.md

RubyGems Maintainability

RubyGems is a package management framework for Ruby.

A package (also known as a library) contains a set of functionality that can be invoked by a Ruby program, such as reading and parsing an XML file. We call these packages "gems" and RubyGems is a tool to install, create, manage and load these packages in your Ruby environment.

RubyGems is also a client for RubyGems.org, a public repository of Gems that allows you to publish a Gem that can be shared and used by other developers. See our guide on publishing a Gem at guides.rubygems.org

Getting Started

Installing and managing a Gem is done through the gem command. To install a Gem such as Nokogiri which lets you read and parse XML in Ruby:

$ gem install nokogiri

RubyGems will download the Nokogiri Gem from RubyGems.org and install it into your Ruby environment.

Finally, inside your Ruby program, load the Nokogiri gem and start parsing your XML:

require 'nokogiri'

Nokogiri.XML('<h1>Hello World</h1>')

For more information about how to use RubyGems, see our RubyGems basics guide at guides.rubygems.org

Requirements

  • RubyGems supports Ruby 3.0 or later.

Installation

RubyGems is already installed in your Ruby environment, you can check the version you have installed by running gem --version in your terminal emulator.

In some cases Ruby & RubyGems may be provided as OS packages. This is not a recommended way to use Ruby & RubyGems. It's better to use a Ruby Version Manager, such as rbenv or chruby. If you still want to use the version provided by your OS package manager, please also use your OS package manager to upgrade rubygems, and disregard any other installation instructions given below.

If you would like to manually install RubyGems:

Install RubyGems by running:

$ ruby setup.rb

For more details and other options, see:

$ ruby setup.rb --help

Upgrading RubyGems

To upgrade to the latest RubyGems, run:

$ gem update --system

See UPGRADING for more details and alternative instructions.

Release policy

RubyGems and Bundler are released in sync, although they do not share their major version number. It is planned that also their major version numbers will be sync'ed in the future.

The release policy is somewhat similar to the release policy of Ruby itself:

  • Frequent patch releases (every 2-4 weeks) including bug fixes, minor enhancements, small features, or even medium sized features declared as experimental for battle testing.
  • Yearly minor releases including bigger features, and minor breaking changes (affecting only edge cases and a very small set of users).
  • Occasional major releases (replacing yearly minors) including major breaking changes.

Documentation

RubyGems uses rdoc for documentation. A compiled set of the docs can be viewed online at rubydoc.

RubyGems also provides a comprehensive set of guides which covers numerous topics such as creating a new gem, security practices and other resources at https://guides.rubygems.org

Getting Help

Filing Tickets

Got a bug and you're not sure? You're sure you have a bug, but don't know what to do next? In any case, let us know about it! The best place for letting the RubyGems team know about bugs or problems you're having is on the RubyGems issues page at GitHub.

Bundler Compatibility

See https://bundler.io/compatibility for known issues.

Supporting

RubyGems is managed by Ruby Central, a non-profit organization that supports the Ruby community through projects like this one, as well as RubyConf, RailsConf, and RubyGems.org. You can support Ruby Central by attending or sponsoring a conference, or by joining as a supporting member.

Contributing

If you'd like to contribute to RubyGems, that's awesome, and we <3 you. Check out our guide to contributing for more information.

Code of Conduct

Everyone interacting in the RubyGems project’s codebases, issue trackers, chat rooms, and mailing lists is expected to follow the contributor code of conduct.