bundler 1.15.2 → 2.4.12

data/doc/contributing/HOW_YOU_CAN_HELP.md

@@ -1,27 +0,0 @@
-# How you can help: your first commits!
-
-If you’re interested in contributing to Bundler, that’s awesome! We’d love your help.
-
-If at any point you get stuck, here's how to [get in touch with the Bundler team for help](GETTING_HELP.md).
-
-## First contribution suggestions
-
-We track [small bugs and features](https://github.com/bundler/bundler/labels/contribution%3A%20small) so that anyone who wants to help can start with something that's not too overwhelming.
-
-Generally, great ways to get started helping out with Bundler are:
-
-  - using prerelease versions (run `gem install bundler --pre`)
-  - [reporting bugs you encounter or suggesting new features](https://github.com/bundler/bundler/issues/new)
-    - see our [issues guide](ISSUES.md) for help on filing issues
-    - see the [new features documentation](../development/NEW_FEATURES.md) for more
-  - adding to or editing [the Bundler documentation website](http://bundler.io) and [Bundler man pages](http://bundler.io/man/bundle.1.html)
-  - [checking issues for completeness](BUG_TRIAGE.md)
-  - closing issues that are not complete
-  - adding a failing test for reproducible [reported bugs](https://github.com/bundler/bundler/issues)
-  - reviewing [pull requests](https://github.com/bundler/bundler/pulls) and suggesting improvements
-  - improving existing code, including suggestions from [PullReview](https://www.pullreview.com/github/bundler/bundler/reviews/master) or [CodeClimate](https://codeclimate.com/github/bundler/bundler)
-  - writing code (no patch is too small! fix typos or bad whitespace)
-    - get started setting up your dev environment with [these instructions](../development/DEVELOPMENT_SETUP.md)
-  - backfilling [unit tests](https://github.com/bundler/bundler/tree/master/spec/bundler) for modules that lack [coverage](https://codeclimate.com/github/bundler/bundler/coverage)
-
-If nothing on those lists looks good, [talk to us](http://slack.bundler.io/), and we'll figure out what you can help with. We can absolutely use your help, no matter what level of programming skill you have at the moment.

data/doc/contributing/ISSUES.md

@@ -1,51 +0,0 @@
-# Filing Issues: a guide
-
-So! You're having problems with Bundler. This file is here to help. If you're running into an error, try reading the rest of this file for help. If you can't figure out how to solve your problem, there are also instructions on how to report a bug.
-
-Before filing an issue, check our [troubleshooting guide](../TROUBLESHOOTING.md) for quick fixes to common issues.
-
-## Documentation
-
-Instructions for common Bundler uses can be found on the [Bundler documentation site](http://bundler.io/).
-
-Detailed information about each Bundler command, including help with common problems, can be found in the [Bundler man pages](http://bundler.io/man/bundle.1.html) or [Bundler Command Line Reference](http://bundler.io/v1.11/commands.html).
-
-## Reporting unresolved problems
-
-Check our [troubleshooting common issues guide](../TROUBLESHOOTING.md) and see if your issues is resolved using the steps provided.
-
-Hopefully the troubleshooting steps above resolved your problem! If things still aren't working the way you expect them to, please let us know so that we can diagnose and hopefully fix the problem you're having.
-
-**The best way to report a bug is by providing a reproduction script.** See these examples:
-
-* [Git environment variables causing install to fail.](https://gist.github.com/xaviershay/6207550)
-* [Multiple gems in a repository cannot be updated independently.](https://gist.github.com/xaviershay/6295889)
-
-A half working script with comments for the parts you were unable to automate is still appreciated.
-
-If you are unable to do that, please include the following information in your report:
-
- - What you're trying to accomplish
- - The command you ran
- - What you expected to happen
- - What actually happened
- - The exception backtrace(s), if any
- - Everything output by running `bundle env`
-
-If your version of Bundler does not have the `bundle env` command, then please include:
-
- - Your `Gemfile`
- - Your `Gemfile.lock`
- - Your Bundler configuration settings (run `bundle config`)
- - What version of bundler you are using (run `bundle -v`)
- - What version of Ruby you are using (run `ruby -v`)
- - What version of Rubygems you are using (run `gem -v`)
- - Whether you are using RVM, and if so what version (run `rvm -v`)
- - Whether you have the `rubygems-bundler` gem, which can break gem executables (run `gem list rubygems-bundler`)
- - Whether you have the `open_gem` gem, which can cause rake activation conflicts (run `gem list open_gem`)
-
-If you have either `rubygems-bundler` or `open_gem` installed, please try removing them and then following the troubleshooting steps above before opening a new ticket.
-
-[Create a gist](https://gist.github.com) containing all of that information, then visit the [Bundler issue tracker](https://github.com/bundler/bundler/issues) and [create a ticket](https://github.com/bundler/bundler/issues/new) describing your problem and linking to your gist.
-
-Thanks for reporting issues and helping make Bundler better!

data/doc/contributing/README.md

@@ -1,38 +0,0 @@
-# Contributing to Bundler
-
-Welcome to Bundler! We are so happy that you're here. We know it can be daunting to joining a new open source project, so here's a quick overview of what you can expect from this documentation.
-
-*Something missing?* Send us a [pull request](../development/PULL_REQUESTS.md)!
-
-**Recommended first steps**
-
-- Join us in the Bundler slack! Generate an invite [here](http://slack.bundler.io/)
-- *If you're interested in helping with code:*
-  - Get a quick overview of our [development process](../development/README.md)
-  - [Setup your machine for development](../development/SETUP.md)
-  - Checkout [How you can help: your first contributions!](HOW_YOU_CAN_HELP.md) for a list of suggestions to get started
-- *If you're interested in helping with documentation:*
-  - Read up on [how documentation works for Bundler](../documentation/README.md)
-  - Learn about our [documentation vision](../documentation/VISION.md)
-
-You can start learning about Bundler by reading [the documentation](http://bundler.io). If you want, you can also read a (lengthy) explanation of [why Bundler exists and what it does](http://bundler.io/rationale.html).
-
-## [How you can help: your first contributions!](HOW_YOU_CAN_HELP.md)
-
-A detailed overview of how to get started contributing to Bundler, including a long list of suggestions for your first project.
-
-## [Bug triage](BUG_TRIAGE.md)
-
-Want to take a stab at processing issues? Start here.
-
-## [Getting help](GETTING_HELP.md)
-
-How to get in touch with folks who can help when you're stuck. Don't worry! This happens to all of us. We're really nice, we promise.
-
-## [Filing issues](ISSUES.md)
-
-We see a lot of issues in the Bundler repo! Use this guide to file informative, actionable issues.
-
-## [Community](COMMUNITY.md)
-
-Learn more about our goals for the Bundler community and the ways you can help us build better together.

data/doc/development/NEW_FEATURES.md

@@ -1,10 +0,0 @@
-# Adding New Features
-
-If you would like to add a new feature to Bundler, please follow these steps:
-
-  1. [Create an issue](https://github.com/bundler/bundler/issues/new) with the [`feature-request` label](https://github.com/bundler/bundler/labels/type:%20feature-request) to discuss your feature.
-  2. Base your commits on the master branch, since we follow [SemVer](http://semver.org) and don't add new features to old releases.
-  3. Commit the code and at least one test covering your changes to a feature branch in your fork.
-  4. Send us a [pull request](PULL_REQUESTS.md) from your feature branch.
-
-If you don't hear back immediately, don’t get discouraged! We all have day jobs, but we respond to most tickets within a day or two.

data/doc/development/PULL_REQUESTS.md

@@ -1,40 +0,0 @@
-# Submitting Pull Requests
-
-Before you submit a pull request, please remember to do the following:
-
-1. Check your code format and style
-2. Run the test suite
-3. Use a meaningful commit message without tags
-
-## Code formatting
-
-Make sure the code formatting and styling adheres to the guidelines. We use RuboCop for this. Lack of formatting adherence will result in automatic Travis build failures.
-
-      $ bin/rubocop -a
-
-## Tests
-
-Prior to submitting your PR, please run the test suite:
-
-      $ bin/rspec
-
-If you are unable to run the entire test suite, please run the unit test suite and at least the integration specs related to the command or domain of Bundler that your code changes relate to.
-
-Ex. For a pull request that changes something with `bundle update`, you might run:
-
-      $ bin/rspec spec/bundler
-      $ bin/rspec spec/commands/update_spec.rb
-
-## Commit messages
-
-Please ensure that the commit messages included in the pull request __do not__ have the following:
-  - `@tag` GitHub user or team references (ex. `@indirect` or `@bundler/core`)
-  - `#id` references to issues or pull requests (ex. `#43` or `bundler/bundler-site#12`)
-
-If you want to use these mechanisms, please instead include them in the pull request description. This prevents multiple notifications or references being created on commit rebases or pull request/branch force pushes.
-
-Additionally, do not use `[ci skip]` or `[skip ci]` mechanisms in your pull request titles/descriptions or commit messages. Every potential commit and pull request should run through Bundler's CI system. This applies to all changes/commits (ex. even a change to just documentation or the removal of a comment).
-
-## CHANGELOG.md
-
-Don't forget to add your changes into the CHANGELOG! If you're submitting documentation, note the changes under the "Documentation" heading.

data/doc/development/README.md

@@ -1,19 +0,0 @@
-# Development
-
-So, you're ready to start contributing to Bundler! You've come to the right place. Here you'll find an overview of how to work on Bundler locally and a description of the process from code to release.
-
-##[Development setup](SETUP.md)
-
-Guidelines for setting up your local development environment.
-
-##[Submitting pull requests](PULL_REQUESTS.md)
-
-An overview of our preferred PR process, including how to run the test suite and what to expect when you submit code for review.
-
-##[Adding new features](NEW_FEATURES.md)
-
-Guidelines for proposing and writing new features for Bundler.
-
-##[Releasing Bundler](RELEASING.md)
-
-A broad-strokes overview of the release process adhered to by the Bundler core team.

data/doc/development/RELEASING.md

@@ -1,9 +0,0 @@
-# Releasing
-
-_Release process documentation is in progress, see [PR 5252](https://github.com/bundler/bundler/pull/5252)._
-
-## Beta testing
-
-Early releases require heavy testing, especially across various system setups. We :heart: testers, and are big fans of anyone who can run `gem install bundler --pre` and try out upcoming releases in their development and staging environments.
-
-There may not always be prereleases or beta versions of Bundler. The Bundler team will tweet from the [@bundlerio account](http://twitter.com/bundlerio) when a prerelease or beta version becomes available. You are also always welcome to try checking out master and building a gem yourself if you want to try out the latest changes.

data/doc/development/SETUP.md

@@ -1,27 +0,0 @@
-# Development setup
-
-Bundler doesn't use a Gemfile to list development dependencies, because when we tried it we couldn't tell if we were awake or it was just another level of dreams. To work on Bundler, you'll probably want to do a couple of things.
-
-1. Install `groff-base` and `graphviz` packages using your package manager, e.g for ubuntu
-
-      $ sudo apt-get install graphviz groff-base -y
-
-   and for OS X (with brew installed)
-
-      $ brew install graphviz homebrew/dupes/groff
-
-2. Install Bundler's development dependencies
-
-      $ bin/rake spec:deps
-
-3. Run the test suite, to make sure things are working
-
-      $ bin/rake spec
-
-4. Set up a shell alias to run Bundler from your clone, e.g. a Bash alias:
-
-      `$ alias dbundle='ruby -I /path/to/bundler/lib /path/to/bundler/exe/bundle'`
-
-## Debugging with `pry`
-
-To dive into the code with Pry: `RUBYOPT=-rpry dbundle` to require pry and then run commands.

data/doc/documentation/README.md

@@ -1,29 +0,0 @@
-# Documentation
-
-Code needs explanation, and sometimes those who know the code well have trouble explaining it to someone just getting into it. Because of that, we welcome documentation suggestions and patches from everyone, especially if they are brand new to using Bundler.
-
-Currently, Bundler has two main sources of documentation:
-
-1. built-in `help` (including usage information and man pages)
-2. [Bundler documentation site](http://bundler.io)
-
-If you have a suggestion or proposed change for [bundler.io](http://bundler.io), please open an issue or send a pull request to the [bundler-site](https://github.com/bundler/bundler-site) repository.
-
-Not sure where to write documentation? In general, follow these guidelines:
-
-* For an explanation of a specific Bundler command (ex: `bundle clean`): make changes to the man pages
-* For longer explanations or usage guides (ex: "Using Bundler with Rails"): create new documentation within the [bundler-site](https://github.com/bundler/bundler-site) repository
-
-If you are unsure where to begin, ping [@feministy](https://github.com/feministy) or [@indirect](https://github.com/indirect) in the Bundler Slack ([get an invite here](../contributing/GETTING_HELP.md)).
-
-## [Writing docs for man pages)](WRITING.md)
-
-If you’d like to submit a patch to the man pages, you're in the right place! Details on editing and previewing changes to man pages can be found here.
-
-## [Documentation vision](VISION.md)
-
-Just like Bundler, we have a grand plan (really, a wish list of sorts) for Bundler documentation. Preview our hopes and dreams for our documentation here.
-
-## Translations
-
-We don't currently have any translations, but please reach out to us if you would like to help get this going.

data/doc/documentation/VISION.md

@@ -1,26 +0,0 @@
-# Documentation vision
-
-Currently, documentation for using Bundler is spread across two places:
-
-1. built-in `help` (including usage information and man pages)
-2. [Bundler documentation site](http://bundler.io)
-
-Additional documentation about using Bundler to publish gems can also be found on the [RubyGems guides](http://guides.rubygems.org/).
-
-## Goals
-
-Bundler documentation should provide users with assistance:
-
-1. Installing Bundler
-2. Using Bundler to manage an application's dependencies
-3. Using Bundler to create, package, and publish gems
-
-Our goal is to provide three types of documentation:
-
-* High level overviews that provide topical guidance
-* Step-by-step tutorials
-* Command-specific reference material for the CLI
-
-Additionally, this documentation should be readily available in a logical place and easy to follow.
-
-Someday, we'd like to create deep-dive reference material about the inner workings of Bundler. However, while this is part of our overall vision for Bundler documentation, it is not the focus of our current work.

data/doc/documentation/WRITING.md

@@ -1,54 +0,0 @@
-# Writing docs for man pages
-
-A primary source of help for Bundler users are the man pages: the output printed when you run `bundle help` (or `bundler help`). These pages can be a little tricky to format and preview, but are pretty straightforward once you get the hang of it.
-
-_Note: `bundler` and `bundle` may be used interchangeably in the CLI. This guide uses `bundle` because it's cuter._
-
-## What goes in man pages?
-
-We use man pages for Bundler commands used in the CLI (command line interface). They can vary in length from large (see `bundle install`) to very short (see `bundle clean`).
-
-To see a list of commands available in the Bundler CLI, type:
-
-      $ bundle help
-
-Our goal is to have a man page for every command.
-
-Don't see a man page for a command? Make a new page and send us a PR! We also welcome edits to existing pages.
-
-## Creating a new man page
-
-To create a new man page, simply create a new `.ronn` file in the `man/` directory.
-
-For example: to create a man page for the command `bundle cookies` (not a real command, sadly), I would create a file `man/bundle-cookies.ronn` and add my documentation there.
-
-## Formatting
-
-Our man pages use ronn formatting, a combination of Markdown and standard man page conventions. It can be a little weird getting used to it at first, especially if you've used Markdown a lot.
-
-[The ronn guide formatting guide](https://rtomayko.github.io/ronn/ronn.7.html) provides a good overview of the common types of formatting.
-
-In general, make your page look like the other pages: utilize sections like `##OPTIONS` and formatting like code blocks and definition lists where appropriate.
-
-If you're not sure if the formatting looks right, that's ok! Make a pull request with what you've got and we'll take a peek.
-
-## Previewing
-
-To preview your changes as they will print out for Bundler users, you'll need to run a series of commands:
-
-```
-$ rake spec:deps
-$ rake man:build
-$ man man/bundle-cookies.1
-```
-
-If you make more changes to `bundle-cookies.ronn`, you'll need to run the `rake man:build` again before previewing.
-
-## Testing
-
-We have tests for our documentation! The most important test file to run before you make your pull request is the one for the `help` command and another for documentation quality.
-
-```
-$ rspec ./spec/commands/help_spec.rb
-$ rspec ./spec/quality_spec.rb
-```

data/exe/bundle_ruby

@@ -1,59 +0,0 @@
-#!/usr/bin/env ruby
-# frozen_string_literal: true
-
-Signal.trap("INT") { exit 1 }
-
-require "bundler/errors"
-require "bundler/ruby_version"
-require "bundler/ruby_dsl"
-require "bundler/shared_helpers"
-
-module Bundler
-  class Dsl
-    include RubyDsl
-
-    attr_accessor :ruby_version
-
-    def initialize
-      @ruby_version = nil
-    end
-
-    def eval_gemfile(gemfile, contents = nil)
-      contents ||= File.open(gemfile, "rb", &:read)
-      instance_eval(contents, gemfile.to_s, 1)
-    rescue SyntaxError => e
-      bt = e.message.split("\n")[1..-1]
-      raise GemfileError, ["Gemfile syntax error:", *bt].join("\n")
-    rescue ScriptError, RegexpError, NameError, ArgumentError => e
-      e.backtrace[0] = "#{e.backtrace[0]}: #{e.message} (#{e.class})"
-      STDERR.puts e.backtrace.join("\n       ")
-      raise GemfileError, "There was an error in your Gemfile," \
-        " and Bundler cannot continue."
-    end
-
-    def source(source, options = {})
-    end
-
-    def gem(name, *args)
-    end
-
-    def group(*args)
-    end
-  end
-end
-
-Bundler::SharedHelpers.major_deprecation("the bundle_ruby executable has been removed in favor of `bundle platform --ruby`")
-
-dsl = Bundler::Dsl.new
-begin
-  dsl.eval_gemfile(Bundler::SharedHelpers.default_gemfile)
-  ruby_version = dsl.ruby_version
-  if ruby_version
-    puts ruby_version
-  else
-    puts "No ruby version specified"
-  end
-rescue Bundler::GemfileError => e
-  puts e.message
-  exit(-1)
-end

data/lib/bundler/cli/package.rb

@@ -1,46 +0,0 @@
-# frozen_string_literal: true
-module Bundler
-  class CLI::Package
-    attr_reader :options
-
-    def initialize(options)
-      @options = options
-    end
-
-    def run
-      Bundler.ui.level = "error" if options[:quiet]
-      Bundler.settings[:path] = File.expand_path(options[:path]) if options[:path]
-      Bundler.settings[:cache_all_platforms] = options["all-platforms"] if options.key?("all-platforms")
-      Bundler.settings[:cache_path] = options["cache-path"] if options.key?("cache-path")
-
-      setup_cache_all
-      install
-
-      # TODO: move cache contents here now that all bundles are locked
-      custom_path = Pathname.new(options[:path]) if options[:path]
-      Bundler.load.cache(custom_path)
-    end
-
-  private
-
-    def install
-      require "bundler/cli/install"
-      options = self.options.dup
-      if Bundler.settings[:cache_all_platforms]
-        options["local"] = false
-        options["update"] = true
-      end
-      Bundler::CLI::Install.new(options).run
-    end
-
-    def setup_cache_all
-      Bundler.settings[:cache_all] = options[:all] if options.key?("all")
-
-      if Bundler.definition.has_local_dependencies? && !Bundler.settings[:cache_all]
-        Bundler.ui.warn "Your Gemfile contains path and git dependencies. If you want "    \
-          "to package them as well, please pass the --all flag. This will be the default " \
-          "on Bundler 2.0."
-      end
-    end
-  end
-end

data/lib/bundler/dep_proxy.rb

@@ -1,46 +0,0 @@
-# frozen_string_literal: true
-module Bundler
-  class DepProxy
-    attr_reader :__platform, :dep
-
-    def initialize(dep, platform)
-      @dep = dep
-      @__platform = platform
-    end
-
-    def hash
-      @hash ||= dep.hash
-    end
-
-    def ==(other)
-      dep == other.dep && __platform == other.__platform
-    end
-
-    alias_method :eql?, :==
-
-    def type
-      @dep.type
-    end
-
-    def name
-      @dep.name
-    end
-
-    def requirement
-      @dep.requirement
-    end
-
-    def to_s
-      s = name.dup
-      s << " (#{requirement})" unless requirement == Gem::Requirement.default
-      s << " #{__platform}" unless __platform == Gem::Platform::RUBY
-      s
-    end
-
-  private
-
-    def method_missing(*args, &blk)
-      @dep.send(*args, &blk)
-    end
-  end
-end

data/lib/bundler/gem_remote_fetcher.rb

@@ -1,42 +0,0 @@
-# frozen_string_literal: true
-require "rubygems/remote_fetcher"
-
-module Bundler
-  # Adds support for setting custom HTTP headers when fetching gems from the
-  # server.
-  #
-  # TODO: Get rid of this when and if gemstash only supports RubyGems versions
-  # that contain https://github.com/rubygems/rubygems/commit/3db265cc20b2f813.
-  class GemRemoteFetcher < Gem::RemoteFetcher
-    attr_accessor :headers
-
-    # Extracted from RubyGems 2.4.
-    def fetch_http(uri, last_modified = nil, head = false, depth = 0)
-      fetch_type = head ? Net::HTTP::Head : Net::HTTP::Get
-      # beginning of change
-      response   = request uri, fetch_type, last_modified do |req|
-        headers.each {|k, v| req.add_field(k, v) } if headers
-      end
-      # end of change
-
-      case response
-      when Net::HTTPOK, Net::HTTPNotModified then
-        response.uri = uri if response.respond_to? :uri
-        head ? response : response.body
-      when Net::HTTPMovedPermanently, Net::HTTPFound, Net::HTTPSeeOther,
-           Net::HTTPTemporaryRedirect then
-        raise FetchError.new("too many redirects", uri) if depth > 10
-
-        location = URI.parse response["Location"]
-
-        if https?(uri) && !https?(location)
-          raise FetchError.new("redirecting to non-https resource: #{location}", uri)
-        end
-
-        fetch_http(location, last_modified, head, depth + 1)
-      else
-        raise FetchError.new("bad response #{response.message} #{response.code}", uri)
-      end
-    end
-  end
-end

data/lib/bundler/gemdeps.rb

@@ -1,28 +0,0 @@
-# frozen_string_literal: true
-module Bundler
-  class Gemdeps
-    def initialize(runtime)
-      @runtime = runtime
-    end
-
-    def requested_specs
-      @runtime.requested_specs
-    end
-
-    def specs
-      @runtime.specs
-    end
-
-    def dependencies
-      @runtime.dependencies
-    end
-
-    def current_dependencies
-      @runtime.current_dependencies
-    end
-
-    def requires
-      @runtime.requires
-    end
-  end
-end

data/lib/bundler/psyched_yaml.rb

@@ -1,27 +0,0 @@
-# frozen_string_literal: true
-# Psych could be a gem, so try to ask for it
-begin
-  gem "psych"
-rescue LoadError
-end if defined?(gem)
-
-# Psych could be in the stdlib
-# but it's too late if Syck is already loaded
-begin
-  require "psych" unless defined?(Syck)
-rescue LoadError
-  # Apparently Psych wasn't available. Oh well.
-end
-
-# At least load the YAML stdlib, whatever that may be
-require "yaml" unless defined?(YAML.dump)
-
-module Bundler
-  # On encountering invalid YAML,
-  # Psych raises Psych::SyntaxError
-  if defined?(::Psych::SyntaxError)
-    YamlLibrarySyntaxError = ::Psych::SyntaxError
-  else # Syck raises ArgumentError
-    YamlLibrarySyntaxError = ::ArgumentError
-  end
-end

data/lib/bundler/ssl_certs/certificate_manager.rb

@@ -1,65 +0,0 @@
-# frozen_string_literal: true
-require "fileutils"
-require "net/https"
-require "openssl"
-
-module Bundler
-  module SSLCerts
-    class CertificateManager
-      attr_reader :bundler_cert_path, :bundler_certs, :rubygems_certs
-
-      def self.update_from!(rubygems_path)
-        new(rubygems_path).update!
-      end
-
-      def initialize(rubygems_path = nil)
-        if rubygems_path
-          rubygems_cert_path = File.join(rubygems_path, "lib/rubygems/ssl_certs")
-          @rubygems_certs = certificates_in(rubygems_cert_path)
-        end
-
-        @bundler_cert_path = File.expand_path("..", __FILE__)
-        @bundler_certs = certificates_in(bundler_cert_path)
-      end
-
-      def up_to_date?
-        rubygems_certs.all? do |rc|
-          bundler_certs.find do |bc|
-            File.basename(bc) == File.basename(rc) && FileUtils.compare_file(bc, rc)
-          end
-        end
-      end
-
-      def update!
-        return if up_to_date?
-
-        FileUtils.rm bundler_certs
-        FileUtils.cp rubygems_certs, bundler_cert_path
-      end
-
-      def connect_to(host)
-        http = Net::HTTP.new(host, 443)
-        http.use_ssl = true
-        http.verify_mode = OpenSSL::SSL::VERIFY_PEER
-        http.cert_store = store
-        http.head("/")
-      end
-
-    private
-
-      def certificates_in(path)
-        Dir[File.join(path, "**/*.pem")].sort
-      end
-
-      def store
-        @store ||= begin
-          store = OpenSSL::X509::Store.new
-          bundler_certs.each do |cert|
-            store.add_file cert
-          end
-          store
-        end
-      end
-    end
-  end
-end