Skip to content
Library packaging and distribution for Ruby.
Branch: master
Clone or download
bundlerbot and deivid-rodriguez Merge #2690
2690: Add missing wrapper r=hsbt a=deivid-rodriguez

# Description:

Fixes #2686.

When the default bundler gem was being installed through `gem update --system`, the proper rubygems wrapper was not being generated. This PR fixes that, and also adds missing wrapper support for `gem install --default` in general.

# Tasks:

- [x] Describe the problem / feature
- [x] Write tests
- [x] Write code to solve the problem
- [ ] Get code review from coworkers / friends

I will abide by the [code of conduct](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md).


Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net>
Latest commit a276784 Mar 21, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
bin bin/gem: remove initial empty line Jan 18, 2019
bundler @ c627124 To use 2-0-stable branch. Jan 7, 2019
hide_lib_for_update
lib Let default installer take care of bundler bins Mar 19, 2019
test/rubygems
util
.gitignore
.gitmodules Run bundler tests on TravisCI Jun 20, 2016
.rubocop.yml Enable `Lint/ParenthesesAsGroupedExpression` cop Mar 19, 2019
.travis.yml Removed needless environmental variable for Travis CI Mar 18, 2019
CODE_OF_CONDUCT.md Auto merge of #1796 - matk0:patch-1, r=indirect Jan 20, 2017
CONTRIBUTING.md Add steps to run bundler tests Mar 11, 2019
History.txt Merge branch '3.0' Mar 12, 2019
LICENSE.txt
MAINTAINERS.txt
MIT.txt
Manifest.txt
POLICIES.md Clarify version policy Nov 22, 2018
README.md
Rakefile
UPGRADING.md move CONTRIBUTING and POLICIES documents to markdown Oct 3, 2018
appveyor.yml
rubygems-update.gemspec Set the development version of master branch. Jan 1, 2019
setup.rb

README.md

RubyGems Travis Build Status Appveyor Build Status 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

Installation

RubyGems is likely already installed in your Ruby environment, you can check by running gem --version in your terminal emulator. In some cases your OS's package manager may install RubyGems as a separate package from Ruby. It's recommended to check with your OS's package manager before installing RubyGems manually.

If you would like to manually install RubyGems:

  • Download from https://rubygems.org/pages/download, unpack, and cd into RubyGems' src
  • OR clone this repository and cd into the repository (make sure to run git submodule update --init)

Install RubyGems by running:

$ ruby setup.rb

Note: You may need to run the install script with admin/root privileges.

For more details and other options, see:

$ ruby setup.rb --help

Upgrading RubyGems

To upgrade to the latest RubyGems, run:

$ gem update --system

Note: You might need to run the command as an administrator or root user.

See UPGRADING for more details and alternative instructions.

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 http://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 http://bundler.io/compatibility for known issues.

Supporting


Ruby Together pays some RubyGems maintainers for their ongoing work. As a grassroots initiative committed to supporting the critical Ruby infrastructure you rely on, Ruby Together is funded entirely by the Ruby community. Contribute today as an individual or even better, as a company, and ensure that RubyGems, Bundler, and other shared tooling is around for years to come.

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.

While some RubyGems contributors are compensated by Ruby Together, the project maintainers make decisions independent of Ruby Together. As a project, we welcome contributions regardless of the author’s affiliation with Ruby Together.

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.

You can’t perform that action at this time.