Library packaging and distribution for Ruby.
Ruby
Latest commit c134d46 Jul 20, 2016 @homu homu Auto merge of #1659 - rubygems:seg-canonical-segments, r=indirect
[Version] Make hash based upon canonical segments

# Description:

Closes #1617.
This makes sure the hash reflects a `canonical_segments` property, which just removes trailing 0s from the numeric and pre-release segments as `<=>` does

# Tasks:

- [ ] Describe the problem / feature
- [ ] Write tests
- [ ] Write code to solve the problem
- [ ] Get code review from coworkers / friends
- [ ] [Squash commits](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html)

I will abide by the [code of conduct](https://github.com/rubygems/rubygems/blob/master/CODE_OF_CONDUCT.md).
Failed to load latest commit information.
.github Correct spelling of environment in Issue template Apr 25, 2016
bin Revert "+ Introduce a deprecate_quiet that respects $VERBOSE. Use in … May 31, 2011
bundler @ a4169b0 Update vendored bundler to account for rack 2 release Jul 12, 2016
hide_lib_for_update Ensure hide_lib_for_update appears in tarfiles Feb 10, 2010
lib Auto merge of #1659 - rubygems:seg-canonical-segments, r=indirect Jul 20, 2016
test/rubygems Auto merge of #1659 - rubygems:seg-canonical-segments, r=indirect Jul 19, 2016
util Run bundler tests on TravisCI Jun 20, 2016
.autotest Fix autotest matching Jan 21, 2014
.document Fix .document for RDoc/hoe Jun 22, 2009
.gitignore You should not have .gemspec lying around May 22, 2014
.gitmodules Run bundler tests on TravisCI Jun 20, 2016
.travis.yml Run bundler tests on TravisCI Jun 20, 2016
CODE_OF_CONDUCT.md Fixes #1503 link from CoC to project maintainers list. Jun 7, 2016
CONTRIBUTING.rdoc Fix one typo in CONTRIBUTING.rdoc May 25, 2016
CVE-2013-4287.txt Improve wording in CVE-2013-4287 Sep 9, 2013
CVE-2013-4363.txt Fix CVE-2013-4363, remove regexp backtracking Sep 24, 2013
CVE-2015-3900.txt Fix version number affected May 14, 2015
History.txt Version 2.6.6 with updated history Jun 22, 2016
LICENSE.txt Remove reference to missing LICENSE file Jan 15, 2012
MAINTAINERS.txt MAINTAINERS.md isn't actually markdown. Mar 30, 2016
MIT.txt Update MIT credits for near-identical bundler code Nov 13, 2013
Manifest.txt Update vendored bundler to account for rack 2 release Jul 12, 2016
POLICIES.rdoc Merge pull request #1518 from segiddins/seg-policies-prs Mar 27, 2016
README.rdoc Made Setup instructions more intuitive. Feb 19, 2016
Rakefile [Rakefile] Fix inferring rubygems-update gem version Jun 21, 2016
UPGRADING.rdoc Update UPGRADING to mention the 1.5.1 and 1.5.2 breakage Feb 10, 2011
appveyor.yml Set TEST_SSL instead of TRAVIS. May 21, 2016
setup.rb Support running with frozen string literals Jan 30, 2016

README.rdoc

RubyGems

Homepage:

rubygems.org

Announcements:

blog.rubygems.org

Documentation:

guides.rubygems.org

Support:

help.rubygems.org

Source:

github.com/rubygems/rubygems

Bugtracker:

github.com/rubygems/rubygems/issues

DESCRIPTION

RubyGems is a package management framework for Ruby.

This gem is an update for the RubyGems software. You must have an installation of RubyGems before this update can be applied.

See Gem for information on RubyGems (or `ri Gem`)

To upgrade to the latest RubyGems, run:

$ gem update --system  # you might need to be an administrator or root

See UPGRADING.rdoc for more details and alternative instructions.


If you don't have RubyGems installed, you can still do it manually:

  • Download from: rubygems.org/pages/download, unpack, and cd there

  • OR clone this repository and cd there

  • Install with: ruby setup.rb # you may need admin/root privilege

For more details and other options, see:

ruby setup.rb --help

GETTING HELP

Support Requests

Are you unsure of how to use RubyGems? Do you think you've found a bug and you're not sure? If that is the case, the best place for you is to file a support request at help.rubygems.org.

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