Library packaging and distribution for Ruby.
Clone or download
bundlerbot and colby-swandale Merge #2404
2404: update rubocop and also use correct pessimistic version r=segiddins a=colby-swandale

# Description:

This PR has 2 parts. Firstly is just updating Rubocop to the latest version. The second part is that the constraint that is specified in the `util/ci` and the `rubygems-update.gemspec` files are not correct. 

Currently, any version that is less then '1.0' would be installed. This is bad because Rubocop could release a new version which changes a cop that will result in our CI breaking. We want to restrict the version of Rubocop to only patch releases within the given pessimistic version constraint.

______________

# Tasks:

- [ ] Describe the problem / feature
- [ ] Write tests
- [ ] 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: Colby Swandale <me@colby.fyi>
Latest commit 81475ee Sep 25, 2018
Permalink
Failed to load latest commit information.
.github configure bors Sep 23, 2018
bin Improve user-facing messages by consistent casing of Ruby/RubyGems Nov 3, 2016
bundler @ a356d8c Bump bundler-1.16.4. Aug 20, 2018
hide_lib_for_update Ensure hide_lib_for_update appears in tarfiles Feb 10, 2010
lib Merge #2406 Sep 25, 2018
test/rubygems Merge #2382 Sep 24, 2018
util update rubocop and also use correct pessimistic version Sep 23, 2018
.document Fix .document for RDoc/hoe Jun 22, 2009
.gitignore Added coverage ability used by simplecov. Feb 23, 2018
.gitmodules Run bundler tests on TravisCI Jun 20, 2016
.rubocop.yml Added new cop for removing trailing-whitespace. Sep 7, 2018
.travis.yml configure bors Sep 23, 2018
CODE_OF_CONDUCT.md Auto merge of #1796 - matk0:patch-1, r=indirect Jan 20, 2017
CONTRIBUTING.rdoc add rubocop as dev dependency and run in CI Apr 1, 2018
History.txt History May 17, 2018
LICENSE.txt Remove reference to missing LICENSE file Jan 15, 2012
MAINTAINERS.txt Added amatsuda to maintainers list. Dec 6, 2017
MIT.txt Update MIT credits for near-identical bundler code Nov 13, 2013
Manifest.txt Update manifest.txt May 29, 2018
POLICIES.rdoc Address feedback from PR comments. Feb 22, 2018
README.md Minor typo May 21, 2018
Rakefile Use correct rubocop version Sep 12, 2018
UPGRADING.rdoc Update UPGRADING to mention the 1.5.1 and 1.5.2 breakage Feb 10, 2011
appveyor.yml Remove appveyor fix Jun 8, 2018
rubygems-update.gemspec update rubocop and also use correct pessimistic version Sep 23, 2018
setup.rb Removed needless condition for old versions of Ruby. May 11, 2018

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.