mirror of
https://github.com/ruby/ruby.git
synced 2022-11-09 12:17:21 -05:00
* lib/rubygems: Update to RubyGems 2.1.3
Fixed installing platform gems Restored concurrent requires Fixed installing gems with extensions with --install-dir Fixed `gem fetch -v` to install the latest version Fixed installing gems with "./" in their files entries * test/rubygems/test_gem_package.rb: Tests for the above. * NEWS: Updated for RubyGems 2.1.3 git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@42938 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
This commit is contained in:
parent
85995e88d4
commit
1daa0b113d
110 changed files with 3493 additions and 4942 deletions
|
@ -9,21 +9,7 @@ class Gem::Commands::YankCommand < Gem::Command
|
|||
include Gem::GemcutterUtilities
|
||||
|
||||
def description # :nodoc:
|
||||
<<-EOF
|
||||
The yank command removes a gem you pushed to a server from the server's
|
||||
index.
|
||||
|
||||
Note that if you push a gem to rubygems.org the yank command does not
|
||||
prevent other people from downloading the gem via the download link.
|
||||
|
||||
Once you have pushed a gem several downloads will happen automatically
|
||||
via the webhooks. If you accidentally pushed passwords or other sensitive
|
||||
data you will need to change them immediately and yank your gem.
|
||||
|
||||
If you are yanking a gem due to intellectual property reasons contact
|
||||
http://help.rubygems.org for permanant removal. Be sure to mention this
|
||||
as the reason for the removal request.
|
||||
EOF
|
||||
'Remove a specific gem version release from RubyGems.org'
|
||||
end
|
||||
|
||||
def arguments # :nodoc:
|
||||
|
@ -35,7 +21,7 @@ as the reason for the removal request.
|
|||
end
|
||||
|
||||
def initialize
|
||||
super 'yank', 'Remove a pushed gem from the index'
|
||||
super 'yank', description
|
||||
|
||||
add_version_option("remove")
|
||||
add_platform_option("remove")
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue