You can clone with
HTTPS or Subversion.
Using the following gemrc file:
install-command still tries to install gems in the system directory, unlike gem install.
I think it's because Gem::DependencyInstaller.new link which used to install the gem within pry doesn't take into consideration gemrc files.
One idea is to use Gem::ConfigFile.new link to get/parse .gemrc files and manually set the gempath from that to DependencyInstaller. Of course we could parse it manually since it's just an yaml file, but this seems easier.
@sent-hil Yes, that sounds like a good approach. FWIW DependencyInstaller accepts many options, one being install_dir & another being user_install. I think we want to hook into user_install.
@robgleeson cool, will use that. Should I assume gempath option in .gemrc accepts only one path? I see some examples online with multiple paths, not sure how to handle that.
@Mon-Ouie Could you post your .gemrc?
sent-hil/pry@a848d62 : this works, but I don't like the doubles ifs.
Also, there're no tests for gem-install?
@kyrylo Err, I think I read the bug report wrong. I assumed gempath was specified in .gemrc and gem-install was ignoring that. Will see how --user-install is being used by rubygems.
Can I get a code review on this? sent-hil/pry@c58ad08
If someone knows a better way to do last spec, we can remove the minitest depedency.
@sent-hil, you shouldn't have deleted your repository.
Command::InstallCommand: honor ".gemrc" switches
Fix issue #666 (install-command doesn't seem to honor gemrc)
Also, prettify various messages from "install-command".