rubygems-update 4.0.21 → 4.1.0.beta1

data/doc/rubygems/CONTRIBUTING.md

@@ -1,231 +0,0 @@
-# How to contribute
-
-Community involvement is essential to RubyGems. We want to keep it as easy as
-possible to contribute changes. There are a few guidelines that we need
-contributors to follow to reduce the time it takes to get changes merged in.
-
-## Guidelines
-
-1.  New features should be coupled with tests.
-
-2.  Ensure that your code blends well with ours:
-    *   No trailing whitespace
-    *   Match indentation (two spaces)
-    *   Match coding style (run `bin/rake rubocop`)
-
-3.  If any new files are added or existing files removed in a commit or PR,
-    please update the `Manifest.txt` accordingly. This can be done by running
-    `bin/rake update_manifest`
-
-4.  Don't modify the history file or version number.
-
-5.  If you have any questions, Feel free to join us on Slack, you can register
-    by signing up at http://slack.bundler.io or file an issue here:
-    http://github.com/ruby/rubygems/issues
-
-
-For more information and ideas on how to contribute to RubyGems ecosystem, see
-here: https://guides.rubygems.org/contributing/
-
-## Getting Started
-
-### Installing dependencies
-
-    bin/rake setup
-
-> **NOTE**: If the above fails with permission related errors, you're most
-> likely using a global Ruby installation (like the one packaged by your OS),
-> which sets `GEM_HOME` to a location regular users can't write to. Consider
-> using a Ruby version manager like [RVM](https://github.com/rvm/rvm),
-> [rbenv](https://github.com/rbenv/rbenv),
-> [chruby](https://github.com/postmodern/chruby) or [asdf](https://github.com/asdf-vm/asdf-ruby). These will install Ruby to a
-> location regular users can write to, so you won't run into permission issues.
-> Alternatively, consider setting `GEM_HOME` environment variable to a writable
-> location with something like `export GEM_HOME=/tmp/rubygems.gems` and try
-> again.
-
-### Manually trying your local changes
-
-To run commands like `gem install` from the repo:
-
-    ruby -Ilib exe/gem install
-
-To run commands like `bundle install` from the repo:
-
-    bundler/bin/bundle install
-
-### Running Tests
-
-To run the entire test suite you can use:
-
-    bin/rake test
-
-To run an individual test file located for example in `test/rubygems/test_deprecate.rb` you can use:
-
-    ruby -Ilib:test:bundler/lib test/rubygems/test_deprecate.rb
-
-And to run an individual test method named `test_default` within a test file, you can use:
-
-    ruby -Ilib:test:bundler/lib test/rubygems/test_deprecate.rb -n /test_default/
-
-### Running bundler tests
-
-To run the entire bundler test suite in parallel (it takes a while), run the following from the `bundler/` subfolder:
-
-    bin/parallel_rspec
-
-There are some realworld higher level specs run in CI, but not run by `bin/parallel_rspec`. You can run those with:
-
-    bin/rake spec:realworld
-
-To run an individual test file location for example in `spec/install/gems/standalone_spec.rb` you can use the following from the `bundler/` subfolder:
-
-    bin/rspec spec/install/gems/standalone_spec.rb
-
-To test Rubygems changes in bundler, set the path to your local Rubygems copy using the `RGV` environment variable:
-
-    RGV=.. bin/rspec spec/install/gems/standalone_spec.rb
-
-### Checking code style
-
-You can check compliance with our code style with
-
-    bin/rake rubocop
-
-Optionally you can configure git hooks with to check this before every commit with
-
-    bin/rake git_hooks
-
-For more information, check [SETUP.md](../bundler/development/SETUP.md) and [DEBUGGING.md](../bundler/development/DEBUGGING.md).
-
-## Issues
-
-RubyGems uses labels to track all issues and pull requests. In order to
-provide guidance to the community this is documentation of how labels are used
-in the rubygems repository.
-
-### Contribution
-
-These labels are made to guide contributors to issue/pull requests that they
-can help with.
-
-*   **good first issue** - The issue described here is considered a good option
-    for a new contributor. We encourage new contributors though to work on
-    whichever issue they find most interesting, the ones labeled here as just
-    estimated to have a reasonable level of complexity for someone new to the
-    code base.
-*   **help wanted** - The issue has not been claimed for work, and is awaiting
-    willing volunteers!
-
-
-### Type
-
-Issues might have a light green `type: *` label,  which describes the type of
-the issue.
-
-*   **bug report** - An issue describing a bug in rubygems. This would be
-    something that is broken, confusing, unexpected behavior etc.
-*   **feature request** - An issue describing a request for a new feature or
-    enhancement.
-*   **question** - An issue that is a more of a question than a call for
-    specific changes in the codebase.
-*   **cleanup** - An issue that proposes cleanups to the code base without
-    fixing a bug or implementing a feature.
-*   **major bump** - This issue  request requires a major version bump
-*   **administrative** - This issue relates to administrative tasks that need
-    to take place as it relates to rubygems
-*   **documentation** - This issue relates to improving the documentation for
-    in this repo. Note that much of the rubygems documentation is here:
-    https://github.com/rubygems/guides
-
-Pull request might have a light orange `rubygems: *` or a light blue `bundler:
-*` label which describes the pull request according to the following criteria:
-
-*   **security fix** - A pull request that fixes a security issue.
-*   **breaking change** - A pull request including any change that requires a
-    major version bump.
-*   **major enhancement** - A pull request including a backwards compatible
-    change worth a special mention in the changelog
-*   **deprecation** - A pull request that introduces a deprecation.
-*   **feature** - A pull request implementing a feature request.
-*   **deprecation** - A pull request that implements a performance improvement.
-*   **documentation** - A pull request introducing documentation improvements
-    worth mentioning to end users.
-*   **minor enhancements** - A pull request introducing small but user visible changes.
-*   **bug fix** - A pull request that fixes a bug report.
-
-In the case of `bundler`, these labels are set by maintainers on PRs and have
-special importance because they are used to automatically build the changelog.
-
-### Workflow / Status
-
-The light yellow `status: *` labels that indicate the state of an  issue,
-where it is in the process from being submitted to being closed.  These are
-listed in rough  progression order from submitted to closed.
-
-*   **triage** - This is an issue or pull request that needs to be properly
-    labeled by a maintainer.
-*   **confirmed** - This issue/pull request has been accepted as valid, but is
-    not yet immediately ready for work.
-*   **ready** - An issue that is available for collaboration. This issue
-    should have existing discussion on the problem, and a description of how
-    to go about solving it.
-*   **working** - An issue that has a specific individual assigned to and
-    planning to do work on it.
-*   **user feedback required** - The issue/pull request is blocked pending
-    more feedback from an end user
-*   **blocked / backlog** - the issue/pull request is currently unable to move
-    forward because of some specific reason, generally this will be a reason
-    that is outside RubyGems or needs feedback from some specific individual
-    or group, and it may be a while before something it is resolved.
-
-
-### Closed Reason
-
-Reasons are why an issue / pull request was closed without being worked on or
-accepted. There should also be more detailed information in the comments. The
-closed reason labels are maroon `closed: *`.
-
-*   **duplicate** - This is a duplicate of an existing bug. The comments must
-    reference the existing issue.
-*   **abandoned** - This is an issue/pull request that has aged off, is no
-    longer applicable or similar.
-*   **declined** - An issue that won't be fixed/implemented or a pull request
-    that is not accepted.
-*   **deprecated** - An issue/pull request that no longer applies to the
-    actively maintained codebase.
-*   **discussion** - An issue/pull that is no longer about a concrete change,
-    and is instead being used for discussion.
-
-
-### Categories
-
-These are aspects of the codebase, or what general area the issue or pull
-request pertains too. Not all issues will have a category. All categorized
-issues have a blue `category: *` label.
-
-*   **gemspec** - related to the gem specification itself
-*   **API** - related to the public supported rubygems API. This is the code
-    API, not a network related API.
-*   **command** - related to something in `Gem::Commands`
-*   **install** - related to gem installations
-*   **documentation** - related to updating / fixing / clarifying
-    documentation or guides
-
-
-### Platforms
-
-If an issue or pull request pertains to only one platform, then it should have
-an appropriate purple `platform: *` label. Current platform labels:
-**windows**, **java**, **osx**, **linux**
-
-### Git
-
-Please sign your commits. Although not required in order for you to contribute,
-it ensures that any code submitted by you wasn't altered while you were
-transferring it, and proves that it was you who submitted it and not someone
-else.
-
-Please see https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work or
-https://help.github.com/en/articles/signing-commits for details on how to
-to generate a signature and automatically sign your commits.

data/doc/rubygems/POLICIES.md

@@ -1,60 +0,0 @@
-## Pull Requests
-
-Contributions to RubyGems are made via GitHub pull requests, which must be
-approved by a project committer other than the author. To approve a PR, a
-maintainer can use GitHubs PR review feature. After that, if the original author
-is happy to merge the PR, she can press the merge button.
-
-## Long-Term Support
-
-RubyGems will support Ruby versions for as long as the Ruby team supports that
-Ruby version. That means that the latest RubyGems release will always support
-the currently-supported Ruby versions, and RubyGems security fixes will be
-released for any RubyGems version that shipped inside a currently-supported
-Ruby version.
-
-### Bugfix Releases
-
-RubyGems generally releases bugfixes from the master branch. We may mix bug
-fixes and new features in the same release. RubyGems does not guarantee it
-will ship bugfix releases for previous minor or major versions.
-
-For example, after RubyGems 2.5 is released, the RubyGems team will not
-provide non-security fixes for RubyGems 2.4, or any earlier versions.
-
-### Security Releases
-
-Security releases will be made for RubyGems minor versions that were included
-in a currently-supported Ruby release.
-
-For example, since RubyGems 2.0 was shipped in Ruby 2.0, RubyGems 2.0 will
-receive security fixes until Ruby 2.0 reaches end-of-life.
-
-### Ruby Version Support
-
-When a Ruby version reaches end-of-life the following minor release of
-RubyGems will drop backwards compatibility with that Ruby version.
-
-For example, since Ruby 2.2 has reached end-of-life, future RubyGems minor
-releases will only support Ruby 2.3 and above. As of this writing RubyGems is
-at version 2.7, so when RubyGems 2.8 is released, it will only support Ruby
-2.3 and later.
-
-## Committer Access
-
-RubyGems committers may lose their commit privileges if they are inactive for
-longer than 12 months. Committer permission may be restored upon request by
-having a pull request merged.
-
-This is designed to improve the maintainability of RubyGems by requiring
-committers to maintain familiarity with RubyGems activity and to improve the
-security of RubyGems by preventing idle committers from having their commit
-permissions compromised or exposed.
-
-## Changing These Policies
-
-These policies were set in order to reduce the burden of maintenance and to keep
-committers current with existing development and policies. RubyGems work is
-primarily volunteer-driven which limits the ability to provide long-term
-support. By joining [Ruby Central](https://rubycentral.org/#/portal/signup) you
-can help extend support for older RubyGems versions.

data/lib/rubygems/request_set/lockfile/parser.rb

@@ -1,344 +0,0 @@
-# frozen_string_literal: true
-
-class Gem::RequestSet::Lockfile::Parser
-  ###
-  # Parses lockfiles
-
-  def initialize(tokenizer, set, platforms, filename = nil)
-    @tokens    = tokenizer
-    @filename  = filename
-    @set       = set
-    @platforms = platforms
-  end
-
-  def parse
-    until @tokens.empty? do
-      token = get
-
-      case token.type
-      when :section then
-        @tokens.skip :newline
-
-        case token.value
-        when "DEPENDENCIES" then
-          parse_DEPENDENCIES
-        when "GIT" then
-          parse_GIT
-        when "GEM" then
-          parse_GEM
-        when "PATH" then
-          parse_PATH
-        when "PLATFORMS" then
-          parse_PLATFORMS
-        else
-          token = get until @tokens.empty? || peek.first == :section
-        end
-      else
-        raise "BUG: unhandled token #{token.type} (#{token.value.inspect}) at line #{token.line} column #{token.column}"
-      end
-    end
-  end
-
-  ##
-  # Gets the next token for a Lockfile
-
-  def get(expected_types = nil, expected_value = nil) # :nodoc:
-    token = @tokens.shift
-
-    if expected_types && !Array(expected_types).include?(token.type)
-      unget token
-
-      message = "unexpected token [#{token.type.inspect}, #{token.value.inspect}], " \
-                "expected #{expected_types.inspect}"
-
-      raise Gem::RequestSet::Lockfile::ParseError.new message, token.column, token.line, @filename
-    end
-
-    if expected_value && expected_value != token.value
-      unget token
-
-      message = "unexpected token [#{token.type.inspect}, #{token.value.inspect}], " \
-                "expected [#{expected_types.inspect}, " \
-                "#{expected_value.inspect}]"
-
-      raise Gem::RequestSet::Lockfile::ParseError.new message, token.column, token.line, @filename
-    end
-
-    token
-  end
-
-  def parse_DEPENDENCIES # :nodoc:
-    while !@tokens.empty? && peek.type == :text do
-      token = get :text
-
-      requirements = []
-
-      case peek[0]
-      when :bang then
-        get :bang
-
-        requirements << pinned_requirement(token.value)
-      when :l_paren then
-        get :l_paren
-
-        loop do
-          op      = get(:requirement).value
-          version = get(:text).value
-
-          requirements << "#{op} #{version}"
-
-          break unless peek.type == :comma
-
-          get :comma
-        end
-
-        get :r_paren
-
-        if peek[0] == :bang
-          requirements.clear
-          requirements << pinned_requirement(token.value)
-
-          get :bang
-        end
-      end
-
-      @set.gem token.value, *requirements
-
-      skip :newline
-    end
-  end
-
-  def parse_GEM # :nodoc:
-    sources = []
-
-    while peek.first(2) == [:entry, "remote"] do
-      get :entry, "remote"
-      data = get(:text).value
-      skip :newline
-
-      sources << Gem::Source.new(data)
-    end
-
-    sources << Gem::Source.new(Gem::DEFAULT_HOST) if sources.empty?
-
-    get :entry, "specs"
-
-    skip :newline
-
-    set = Gem::Resolver::LockSet.new sources
-    last_specs = nil
-
-    while !@tokens.empty? && peek.type == :text do
-      token = get :text
-      name = token.value
-      column = token.column
-
-      case peek[0]
-      when :newline then
-        last_specs.each do |spec|
-          spec.add_dependency Gem::Dependency.new name if column == 6
-        end
-      when :l_paren then
-        get :l_paren
-
-        token = get [:text, :requirement]
-        type = token.type
-        data = token.value
-
-        if type == :text && column == 4
-          version, platform = data.split "-", 2
-
-          platform =
-            platform ? Gem::Platform.new(platform) : Gem::Platform::RUBY
-
-          last_specs = set.add name, version, platform
-        else
-          dependency = parse_dependency name, data
-
-          last_specs.each do |spec|
-            spec.add_dependency dependency
-          end
-        end
-
-        get :r_paren
-      else
-        raise "BUG: unknown token #{peek}"
-      end
-
-      skip :newline
-    end
-
-    @set.sets << set
-  end
-
-  def parse_GIT # :nodoc:
-    get :entry, "remote"
-    repository = get(:text).value
-
-    skip :newline
-
-    get :entry, "revision"
-    revision = get(:text).value
-
-    skip :newline
-
-    type = peek.type
-    value = peek.value
-    if type == :entry && %w[branch ref tag].include?(value)
-      get
-      get :text
-
-      skip :newline
-    end
-
-    get :entry, "specs"
-
-    skip :newline
-
-    set = Gem::Resolver::GitSet.new
-    set.root_dir = @set.install_dir
-
-    last_spec = nil
-
-    while !@tokens.empty? && peek.type == :text do
-      token = get :text
-      name = token.value
-      column = token.column
-
-      case peek[0]
-      when :newline then
-        last_spec.add_dependency Gem::Dependency.new name if column == 6
-      when :l_paren then
-        get :l_paren
-
-        token = get [:text, :requirement]
-        type = token.type
-        data = token.value
-
-        if type == :text && column == 4
-          last_spec = set.add_git_spec name, data, repository, revision, true
-        else
-          dependency = parse_dependency name, data
-
-          last_spec.add_dependency dependency
-        end
-
-        get :r_paren
-      else
-        raise "BUG: unknown token #{peek}"
-      end
-
-      skip :newline
-    end
-
-    @set.sets << set
-  end
-
-  def parse_PATH # :nodoc:
-    get :entry, "remote"
-    directory = get(:text).value
-
-    skip :newline
-
-    get :entry, "specs"
-
-    skip :newline
-
-    set = Gem::Resolver::VendorSet.new
-    last_spec = nil
-
-    while !@tokens.empty? && peek.first == :text do
-      token = get :text
-      name = token.value
-      column = token.column
-
-      case peek[0]
-      when :newline then
-        last_spec.add_dependency Gem::Dependency.new name if column == 6
-      when :l_paren then
-        get :l_paren
-
-        token = get [:text, :requirement]
-        type = token.type
-        data = token.value
-
-        if type == :text && column == 4
-          last_spec = set.add_vendor_gem name, directory
-        else
-          dependency = parse_dependency name, data
-
-          last_spec.dependencies << dependency
-        end
-
-        get :r_paren
-      else
-        raise "BUG: unknown token #{peek}"
-      end
-
-      skip :newline
-    end
-
-    @set.sets << set
-  end
-
-  def parse_PLATFORMS # :nodoc:
-    while !@tokens.empty? && peek.first == :text do
-      name = get(:text).value
-
-      @platforms << name
-
-      skip :newline
-    end
-  end
-
-  ##
-  # Parses the requirements following the dependency +name+ and the +op+ for
-  # the first token of the requirements and returns a Gem::Dependency object.
-
-  def parse_dependency(name, op) # :nodoc:
-    return Gem::Dependency.new name, op unless peek[0] == :text
-
-    version = get(:text).value
-
-    requirements = ["#{op} #{version}"]
-
-    while peek.type == :comma do
-      get :comma
-      op      = get(:requirement).value
-      version = get(:text).value
-
-      requirements << "#{op} #{version}"
-    end
-
-    Gem::Dependency.new name, requirements
-  end
-
-  private
-
-  def skip(type) # :nodoc:
-    @tokens.skip type
-  end
-
-  ##
-  # Peeks at the next token for Lockfile
-
-  def peek # :nodoc:
-    @tokens.peek
-  end
-
-  def pinned_requirement(name) # :nodoc:
-    requirement = Gem::Dependency.new name
-    specification = @set.sets.flat_map do |set|
-      set.find_all(requirement)
-    end.compact.first
-
-    specification&.version
-  end
-
-  ##
-  # Ungets the last token retrieved by #get
-
-  def unget(token) # :nodoc:
-    @tokens.unshift token
-  end
-end