RBENV-doctor warning: "rbenv-bundler is considerd harmful"

[WarthogARJ]

Hi,
After installing rbenv-bundler without obvious issues, I ran the so-called rbenv-doctor script and it gave me a warning:
"rbenv-bundler is considered harmful. Please remove the plugin..."

Please forgive me if I am describing a known issue: but I did not see any warning in HomeBrew/Git about any issues between rbenv and rbenv-bundler.

Up until installing rbenv-bundler I had no problem with rbenv, or anything else with ruby.
The rbenv-doctor script is described here:
"https://github.com/rbenv/rbenv-installer/blob/main/bin/rbenv-doctor"
The script is:
"curl -fsSL https://github.com/rbenv/rbenv-installer/raw/main/bin/rbenv-doctor | bash"
The rbenv-bundler plug-in warning is initiated at line 205 in the code.

Before I installed rebenv-bunder the rbenv-doctor reported all was OK:
$ Checking for rbenv' in PATH: /usr/local/bin/rbenv $ Checking for rbenv shims in PATH: OK $ Checking rbenv install' support: /usr/local/bin/rbenv-install (ruby-build 20220825)
$ Counting installed Ruby versions: 1 versions
$ Checking RubyGems settings: OK
$ Auditing installed plugins: OK"

But after installing rbenv-bunder, it was the same except for the plug-in warning at last line:
"Note: do not install rbenv-bundler
$ Auditing installed plugins: warning
$ rbenv-bundler is considered harmful. Please remove the plugin and `rm -rf $(rbenv root)/shims && rbenv rehash'."

After removing rbenv-bundler, the rbenv-doctor script gave the same message as at first: "all OK".

I am pretty new to ruby, and normally just use HomeBrew and Github to download things.
I tried to look at what might be the issue, but nothing was obvious.

Forgve me for stating the obvious, but to me, it sems there is either a problem with rbenv-bundler, or else the developers of rbenv need to update their doctor script.

In any event, until this is cleared up, it seems there should be a notice in rbenv-bundler about this.

[carsomyr]

Found it with a trip down memory lane: #32. Many of the issues mentioned can be resolved, and in the meantime I will add a warning when the plugin first installs.