Feature request: gem install to allow --user-install option

[Rumbles]

Setup

I was hoping I could replicate the following using salt, as a given user (not root) I would run:

gem install --user-install bundler

Looking at the docs I can't see a way to do --user-install, someone suggested that gem might default to user install if you're non-root, but when I tested it I got this from the command line:

$ gem install bundler
Fetching: bundler-1.11.2.gem (100%)
ERROR:  While executing gem ... (Errno::EACCES)
    Permission denied @ dir_s_mkdir - /var/lib/gems

As per: http://serverfault.com/questions/762124/installing-a-gem-using-saltstack-with-user-install-option

Steps to Reproduce Issue

Run a gem install --user-install via a salt manifest

Versions Report

$ salt --versions-report
                  Salt: 2015.5.3
                Python: 2.7.6 (default, Jun 22 2015, 17:58:13)
                Jinja2: 2.7.2
              M2Crypto: 0.21.1
        msgpack-python: 0.3.0
          msgpack-pure: Not Installed
              pycrypto: 2.6.1
               libnacl: Not Installed
                PyYAML: 3.10
                 ioflo: Not Installed
                 PyZMQ: 14.0.1
                  RAET: Not Installed
                   ZMQ: 4.0.4
                  Mako: 0.9.1
               Tornado: Not Installed
 Debian source package: 2015.5.3+ds-1trusty1

[jfindlay]

@Rumbles, thanks for reporting. This would be good to have.

[disaster123]

i'm using the following work around. Create a .gemrc file in your user account:

cat .gemrc

install: --user-install
update: --user-install
uninstall: --user-install

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[disaster123]

Issue is still present.

[stale[bot]]

Thank you for updating this issue. It is no longer marked as stale.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[disaster123]

Still valid

[stale[bot]]

Thank you for updating this issue. It is no longer marked as stale.