rubygems-update 3.1.4 → 3.2.14

data/Gemfile

@@ -1,8 +0,0 @@
-source "https://rubygems.org"
-
-gem "builder", "~> 3.0"
-gem "rdoc", "~> 6.0"
-gem "rake", "~> 12.0"
-gem "minitest", "~> 5.0"
-gem "simplecov", "~> 0"
-gem "rubocop", "~> 0.74.0"

data/Gemfile.lock

@@ -1,43 +0,0 @@
-GEM
-  remote: https://rubygems.org/
-  specs:
-    ast (2.4.0)
-    builder (3.2.3)
-    docile (1.3.2)
-    jaro_winkler (1.5.4)
-    json (2.2.0)
-    minitest (5.13.0)
-    parallel (1.19.1)
-    parser (2.6.5.0)
-      ast (~> 2.4.0)
-    rainbow (3.0.0)
-    rake (12.3.3)
-    rdoc (6.2.0)
-    rubocop (0.74.0)
-      jaro_winkler (~> 1.5.1)
-      parallel (~> 1.10)
-      parser (>= 2.6)
-      rainbow (>= 2.2.2, < 4.0)
-      ruby-progressbar (~> 1.7)
-      unicode-display_width (>= 1.4.0, < 1.7)
-    ruby-progressbar (1.10.1)
-    simplecov (0.17.1)
-      docile (~> 1.1)
-      json (>= 1.8, < 3)
-      simplecov-html (~> 0.10.0)
-    simplecov-html (0.10.2)
-    unicode-display_width (1.6.0)
-
-PLATFORMS
-  ruby
-
-DEPENDENCIES
-  builder (~> 3.0)
-  minitest (~> 5.0)
-  rake (~> 12.0)
-  rdoc (~> 6.0)
-  rubocop (~> 0.74.0)
-  simplecov (~> 0)
-
-BUNDLED WITH
-   2.0.2

data/bundler/CODE_OF_CONDUCT.md

@@ -1,136 +0,0 @@
-# Bundler Code of Conduct
-
-## When Something Happens
-
-If you see a Code of Conduct violation, follow these steps:
-
-1.  Let the person know that what they did is not appropriate and ask them to stop and/or edit their message(s).
-2.  That person should immediately stop the behavior and correct the issue.
-3.  If this doesn't happen, or if you're uncomfortable speaking up, [contact admins](#contacting-admins).
-4.  As soon as available, an admin will join, identify themselves, and take [further action (see below)](#further-enforcement), starting with a warning, then temporary deactivation, then long-term deactivation.
-
-When reporting, please include any relevant details, links, screenshots, context, or other information that may be used to better understand and resolve the situation.
-
-**The admin team will prioritize the well-being and comfort of the recipients of the violation over the comfort of the violator.** See [some examples below](#enforcement-examples).
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as members of the Bundler community pledge to making participation in our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, technical preferences, nationality, personal appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment include:
-
--   Using welcoming and inclusive language.
--   Being respectful of differing viewpoints and experiences.
--   Gracefully accepting constructive feedback.
--   Focusing on what is best for the community.
--   Showing empathy and kindness towards other community members.
-
-Examples of unacceptable behavior by participants include:
-
--   The use of sexualized language or imagery and unwelcome sexual attention or advances, including when simulated online. The only exception to sexual topics is channels/spaces specifically for topics of sexual identity.
--   Trolling, insulting/derogatory comments, and personal or political attacks.
--   Casual mention of slavery or indentured servitude and/or false comparisons of one's occupation or situation to slavery. Please consider using or asking about alternate terminology when referring to such metaphors in technology.
--   Making light of/making mocking comments about trigger warnings and content warnings.
--   Public or private harassment, deliberate intimidation, or threats.
--   Publishing others' private information, such as a physical or electronic address, without explicit permission. This includes any sort of "outing" of any aspect of someone's identity without their consent.
--   Publishing screenshots or quotes, especially from identity channels, without all quoted users' _explicit_ consent.
--   Publishing or telling others that a member belongs to a particular identity channel without asking their consent first.
--   Publishing of non-harassing private communication.
--   Any of the above even when [presented as "ironic" or "joking"](https://en.wikipedia.org/wiki/Hipster_racism).
--   Any attempt to present "reverse-ism" versions of the above as violations. Examples of reverse-isms are "reverse racism", "reverse sexism", "heterophobia", and "cisphobia".
--   Unsolicited explanations under the assumption that someone doesn't already know it. Ask before you teach! Don't assume what people's knowledge gaps are.
--   [Feigning or exaggerating surprise](https://www.recurse.com/manual#no-feigned-surprise) when someone admits to not knowing something.
--   "[Well-actuallies](https://www.recurse.com/manual#no-well-actuallys)"
--   Other conduct which could reasonably be considered inappropriate in a professional or community setting.
-
-## Scope
-
-This Code of Conduct applies both within community spaces and in other spaces involving the community. This includes the GitHub repository, the Bundler Slack instance, the Bundler Twitter community, private email communications in the context of the community, and any events where members of the community are participating, as well as adjacent communities and venues affecting the community's members.
-
-Depending on the violation, the admins may decide that violations of this code of conduct that have happened outside of the scope of the community may deem an individual unwelcome, and take appropriate action to maintain the comfort and safety of its members.
-
-This Code of Conduct is detailed for the purpose of removing ambiguity, not for the sake of strictness. It is the sincere hope of admins that it helps foster mutual understanding, and the creation of a space where everyone can participate in a way relevant to the project itself, without things going horribly due to accidental/well-intentioned toe stepping. Please be kind to one another!
-
-## Admin Enforcement Process
-
-Once the admins get involved, they will follow a documented series of steps and do their best to preserve the well-being of community members. This section covers actual concrete steps.
-
-### Contacting Admins
-
-You may get in touch with the Bundler admin team through any of the following methods:
-
-- Email [the Bundler maintainers](https://bundler.io/contributors.html) as a group at [team@bundler.io](mailto:team@bundler.io).
-- Directly message any maintainer in private (through Slack, Twitter, email, or other available option) if that is more comfortable
-
-### Further Enforcement
-
-If you've already followed the [initial enforcement steps](#enforcement), these are the steps admins will take for further enforcement, as needed:
-
-1.  Repeat the request to stop.
-2.  If the person doubles down, they will be removed from the discussion (where possible), and given an official warning.
-3.  If the behavior continues or is repeated later, the person will be blocked/deactivated for 24 hours.
-4.  If the behavior continues or is repeated after the temporary deactivation, a long-term (6-12mo) deactivation will be used.
-
-On top of this, admins may remove any offending messages, images, contributions, etc, as they deem necessary.
-
-Admins reserve full rights to skip any of these steps, at their discretion, if the violation is considered to be a serious and/or immediate threat to the health and well-being of members of the community. These include any threats, serious physical or verbal attacks, and other such behavior that would be completely unacceptable in any social setting that puts our members at risk.
-
-Members expelled from events or venues with any sort of paid attendance will not be refunded.
-
-### Who Watches the Watchers?
-
-Admins and other leaders who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the community's leadership. These may include anything from removal from the admin team to a permanent ban from the community.
-
-### Enforcement Examples
-
-#### The Best Case
-
-The vast majority of situations work out like this, in our experience. This interaction is common, and generally positive.
-
-> Alex: "Yeah I used X and it was really crazy!"
-
-> Patt: "Hey, could you not use that word? What about 'ridiculous' instead?"
-
-> Alex: "oh sorry, sure." -> edits old message to say "it was really confusing!"
-
-#### The Admin Case
-
-Sometimes, though, you need to get admins involved. Admins will do their best to resolve conflicts, but people who were harmed by something **will take priority**.
-
-> Patt: "Honestly, sometimes I just really hate using $language and anyone who uses it probably sucks at their job."
-
-> Alex: "Whoa there, could you dial it back a bit? There's a CoC thing about attacking folks' tech use like that."
-
-> Patt: "I'm not attacking anyone, are you deaf?"
-
-> Alex: _DMs admin_ "hey uh. Can someone look at #general? Patt is getting a bit aggro. I tried to nudge them about it, but nope."
-
-> MxAdmin1: <joins #general> "Hey Patt, admin here. Could you tone it down? This sort of attack is really not okay in this space."
-
-> Patt: "Leave me alone I haven't said anything bad wtf is wrong with you."
-
-> MxAdmin1: _removes patt_ _DMs patt_ "I mean it. Please refer to the CoC over at bundler.io/conduct.html if you have questions, but you can consider this an actual warning. I'd appreciate it if you reworded your messages in #general, since they made folks there uncomfortable. Let's try and be kind, yeah?"
-
-> Patt: _Replies to DM_ "@mxadmin1 Okay sorry. I'm just frustrated and I'm kinda burnt out and I guess I got carried away. I'll DM Alex a note apologizing and edit my messages. Sorry for the trouble."
-
-> MxAdmin1: _Replies to DM_ "@patt Thanks for that. I hear you on the stress. Burnout sucks :/. Have a good one!"
-
-#### The Nope Case
-
-> PepeTheFrog🐸: "Hi, I am a literal actual nazi and I think white supremacists are quite fashionable."
-
-> Patt: "NOOOOPE. OH NOPE NOPE."
-
-> Alex: "JFC NO. NOPE. `/admin nope nope nope @ #javascript`"
-
-> MxAdmin1: "👀 Nope. NOPE NOPE NOPE. 🔥"
-
-> PepeTheFrog🐸 has been deactivated.
-
-## Attribution
-
-This Code of Conduct is adapted from the [package.community Code of Conduct], adapted from the [WeAllJS Code of Conduct](https://wealljs.org/code-of-conduct), itself adapted from [Contributor Covenant](https://contributor-covenant.org) version 1.4, available at [https://contributor-covenant.org/version/1/4](https://contributor-covenant.org/version/1/4), as well as the LGBTQ in Technology Slack [Code of Conduct](https://lgbtq.technology/coc.html).
-
-Additional thanks to [Contributor Covenant](https://contributor-covenant.org) for the [default code of conduct](https://github.com/bundler/bundler/blob/master/lib/bundler/templates/newgem/CODE_OF_CONDUCT.md.tt) included in generated gems.

data/bundler/lib/bundler/vendor/molinillo/lib/molinillo/compatibility.rb

@@ -1,26 +0,0 @@
-# frozen_string_literal: true
-
-module Bundler::Molinillo
-  # Hacks needed for old Ruby versions.
-  module Compatibility
-    module_function
-
-    if [].respond_to?(:flat_map)
-      # Flat map
-      # @param [Enumerable] enum an enumerable object
-      # @block the block to flat-map with
-      # @return The enum, flat-mapped
-      def flat_map(enum, &blk)
-        enum.flat_map(&blk)
-      end
-    else
-      # Flat map
-      # @param [Enumerable] enum an enumerable object
-      # @block the block to flat-map with
-      # @return The enum, flat-mapped
-      def flat_map(enum, &blk)
-        enum.map(&blk).flatten(1)
-      end
-    end
-  end
-end

data/bundler/man/bundle-add.1.txt

@@ -1,58 +0,0 @@
-BUNDLE-ADD(1)							 BUNDLE-ADD(1)
-
-
-
-NAME
-       bundle-add - Add gem to the Gemfile and run bundle install
-
-SYNOPSIS
-       bundle	  add	  GEM_NAME     [--group=GROUP]	   [--version=VERSION]
-       [--source=SOURCE]   [--git=GIT]	 [--branch=BRANCH]    [--skip-install]
-       [--strict] [--optimistic]
-
-DESCRIPTION
-       Adds  the  named  gem  to  the  Gemfile	and run bundle install. bundle
-       install can be avoided by using the flag --skip-install.
-
-       Example:
-
-       bundle add rails
-
-       bundle add rails --version "< 3.0, > 1.1"
-
-       bundle add rails  --version  "~>  5.0.0"  --source  "https://gems.exam-
-       ple.com" --group "development"
-
-       bundle add rails --skip-install
-
-       bundle add rails --group "development, test"
-
-OPTIONS
-       --version, -v
-	      Specify version requirements(s) for the added gem.
-
-       --group, -g
-	      Specify  the  group(s) for the added gem. Multiple groups should
-	      be separated by commas.
-
-       --source, , -s
-	      Specify the source for the added gem.
-
-       --git  Specify the git source for the added gem.
-
-       --branch
-	      Specify the git branch for the added gem.
-
-       --skip-install
-	      Adds the gem to the Gemfile but does not install it.
-
-       --optimistic
-	      Adds optimistic declaration of version
-
-       --strict
-	      Adds strict declaration of version
-
-
-
-
-				 January 2020			 BUNDLE-ADD(1)

data/bundler/man/bundle-binstubs.1.txt

@@ -1,48 +0,0 @@
-BUNDLE-BINSTUBS(1)					    BUNDLE-BINSTUBS(1)
-
-
-
-NAME
-       bundle-binstubs - Install the binstubs of the listed gems
-
-SYNOPSIS
-       bundle binstubs GEM_NAME [--force] [--path PATH] [--standalone]
-
-DESCRIPTION
-       Binstubs  are  scripts  that wrap around executables. Bundler creates a
-       small Ruby file (a binstub) that loads Bundler, runs the  command,  and
-       puts  it  into  bin/. Binstubs are a shortcut-or alternative- to always
-       using bundle exec. This gives you a file that can be run directly,  and
-       one  that  will always run the correct gem version used by the applica-
-       tion.
-
-       For example, if you run bundle binstubs rspec-core, Bundler will create
-       the file bin/rspec. That file will contain enough code to load Bundler,
-       tell it to load the bundled gems, and then run rspec.
-
-       This command generates binstubs for executables in  GEM_NAME.  Binstubs
-       are  put into bin, or the --path directory if one has been set. Calling
-       binstubs with [GEM [GEM]] will create binstubs for all given gems.
-
-OPTIONS
-       --force
-	      Overwrite existing binstubs if they exist.
-
-       --path The location to install the specified binstubs to. This defaults
-	      to bin.
-
-       --standalone
-	      Makes  binstubs  that  can work without depending on Rubygems or
-	      Bundler at runtime.
-
-       --shebang
-	      Specify a different shebang executable  name  than  the  default
-	      (default 'ruby')
-
-BUNDLE INSTALL --BINSTUBS
-       To  create  binstubs  for  all  the  gems in the bundle you can use the
-       --binstubs flag in bundle install(1) bundle-install.1.html.
-
-
-
-				 January 2020		    BUNDLE-BINSTUBS(1)

data/bundler/man/bundle-cache.1.txt

@@ -1,78 +0,0 @@
-BUNDLE-CACHE(1) 					       BUNDLE-CACHE(1)
-
-
-
-NAME
-       bundle-cache - Package your needed .gem files into your application
-
-SYNOPSIS
-       bundle cache
-
-DESCRIPTION
-       Copy  all of the .gem files needed to run the application into the ven-
-       dor/cache   directory.	In   the   future,   when   running    [bundle
-       install(1)][bundle-install], use the gems in the cache in preference to
-       the ones on rubygems.org.
-
-GIT AND PATH GEMS
-       The bundle cache command can also package :git and  :path  dependencies
-       besides	.gem  files. This needs to be explicitly enabled via the --all
-       option. Once used, the --all option will be remembered.
-
-SUPPORT FOR MULTIPLE PLATFORMS
-       When using gems that have different packages for  different  platforms,
-       Bundler	supports caching of gems for other platforms where the Gemfile
-       has been resolved (i.e. present in the lockfile) in vendor/cache.  This
-       needs  to  be enabled via the --all-platforms option. This setting will
-       be remembered in your local bundler configuration.
-
-REMOTE FETCHING
-       By default, if you run bundle install(1)](bundle-install.1.html)  after
-       running bundle cache(1) bundle-cache.1.html, bundler will still connect
-       to rubygems.org to check whether a platform-specific gem exists for any
-       of the gems in vendor/cache.
-
-       For instance, consider this Gemfile(5):
-
-
-
-	   source "https://rubygems.org"
-
-	   gem "nokogiri"
-
-
-
-       If you run bundle cache under C Ruby, bundler will retrieve the version
-       of nokogiri for the "ruby" platform. If you deploy  to  JRuby  and  run
-       bundle  install,  bundler  is  forced  to check to see whether a "java"
-       platformed nokogiri exists.
-
-       Even though the nokogiri gem  for  the  Ruby  platform  is  technically
-       acceptable  on  JRuby, it has a C extension that does not run on JRuby.
-       As a result, bundler will, by default, still connect to rubygems.org to
-       check  whether  it  has	a version of one of your gems more specific to
-       your platform.
-
-       This problem is also not limited to  the  "java"  platform.  A  similar
-       (common) problem can happen when developing on Windows and deploying to
-       Linux, or even when developing on OSX and deploying to Linux.
-
-       If you know for sure that the gems packaged in vendor/cache are	appro-
-       priate  for the platform you are on, you can run bundle install --local
-       to skip checking for more appropriate gems, and use the	ones  in  ven-
-       dor/cache.
-
-       One  way  to be sure that you have the right platformed versions of all
-       your gems is to run bundle cache on an identical machine and  check  in
-       the  gems. For instance, you can run bundle cache on an identical stag-
-       ing box during your staging process,  and  check  in  the  vendor/cache
-       before deploying to production.
-
-       By  default,  bundle  cache(1)  bundle-cache.1.html  fetches  and  also
-       installs the gems to the default location. To package the  dependencies
-       to  vendor/cache without installing them to the local install location,
-       you can run bundle cache --no-install.
-
-
-
-				 January 2020		       BUNDLE-CACHE(1)

data/bundler/man/bundle-check.1.txt

@@ -1,33 +0,0 @@
-BUNDLE-CHECK(1) 					       BUNDLE-CHECK(1)
-
-
-
-NAME
-       bundle-check - Verifies if dependencies are satisfied by installed gems
-
-SYNOPSIS
-       bundle check [--dry-run] [--gemfile=FILE] [--path=PATH]
-
-DESCRIPTION
-       check  searches the local machine for each of the gems requested in the
-       Gemfile. If all gems are found, Bundler prints a  success  message  and
-       exits with a status of 0.
-
-       If not, the first missing gem is listed and Bundler exits status 1.
-
-OPTIONS
-       --dry-run
-	      Locks the [Gemfile(5)][Gemfile(5)] before running the command.
-
-       --gemfile
-	      Use  the	specified  gemfile  instead  of  the [Gemfile(5)][Gem-
-	      file(5)].
-
-       --path Specify a different path than the system	default  ($BUNDLE_PATH
-	      or  $GEM_HOME).  Bundler	will  remember	this  value for future
-	      installs on this machine.
-
-
-
-
-				 January 2020		       BUNDLE-CHECK(1)

data/bundler/man/bundle-clean.1.txt

@@ -1,26 +0,0 @@
-BUNDLE-CLEAN(1) 					       BUNDLE-CLEAN(1)
-
-
-
-NAME
-       bundle-clean - Cleans up unused gems in your bundler directory
-
-SYNOPSIS
-       bundle clean [--dry-run] [--force]
-
-DESCRIPTION
-       This  command  will  remove  all unused gems in your bundler directory.
-       This is useful when you have made many changes to  your	gem  dependen-
-       cies.
-
-OPTIONS
-       --dry-run
-	      Print the changes, but do not clean the unused gems.
-
-       --force
-	      Force a clean even if --path is not set.
-
-
-
-
-				 January 2020		       BUNDLE-CLEAN(1)