I have several gem dylibs that have a line matching "(compatibility "
with no file path preceding it.

https://github.com/rubygems/rubygems/commit/de9dc2bdc4

https://github.com/rubygems/rubygems/commit/e4f70a3e4f

https://github.com/rubygems/rubygems/commit/40cf54d256

https://github.com/rubygems/rubygems/commit/38a0bdc123

https://github.com/rubygems/rubygems/commit/bf63859e1e

https://github.com/rubygems/rubygems/commit/0aae094c89

https://github.com/rubygems/rubygems/commit/e6aa8aabcd

- The command can either be run using:

  1. `bundle doctor --ssl`
  2. `bundle doctor ssl`

  The later is most useful when you need to specify
  custom ssl options (such as the verify mode or the
  TLS version when running the diagnostic).

  The implementation will follow in the next commits.

https://github.com/rubygems/rubygems/commit/993d12874c

- See explanation in previous commit https://github.com/rubygems/rubygems/commit/170890befb4c

https://github.com/rubygems/rubygems/commit/8f1b5a4479

- Adding a new `ssl` option to bundle doctor will make the `Doctor`
  command quite bloated. The "diagnose ssl" option will also have
  children option to allow passing which host or which tls version
  you want to diagnose and I feel these options don't belong in the
  doctor command.
  So my intention in this commit is to prepare to have a new `Doctor`
  subcommand and allow for better organisation of the code:

  The command will be:

  `bundle doctor` -> Run exactly the same as before.
  `bundle doctor --ssl` -> Run the doctor command and diagnose SSL
  with default options (rubygems.org as the host and verify peer as
  the verify mode)
  `bundle doctor ssl --host github.com` -> Run the ssl subcommand and
  pass a specific host.

  This commit just renames a file in order to avoid big diff chunks.