Fails with sudo because of ssh key error

[jdrago999]

Hi -

When running as a non-root user I can clone the repo, but cannot install the gem.

Under sudo I can install the gem, but cloning the repo fails because of ssh key error.

To solve this problem I propose the following:

• add an additional option --sudo which would cause the 'install' part to be done via sudo (on supporting platforms).

I'd rather this functionality become part of the 'specific_install' gem than create a separate project due to this one small feature.

Thoughts?

[rdp]

I'd be down with that, pull request welcome :)

On Tue, Oct 13, 2015 at 12:41 PM, John Drago notifications@github.com
wrote:

Hi -

When running as a non-root user I can clone the repo, but cannot install
the gem.

Under sudo I can install the gem, but cloning the repo fails because of
ssh key error.

To solve this problem I propose the following:

• add an additional option --sudo which would cause the 'install' part
  to be done via sudo (on supporting platforms).

I'd rather this functionality become part of the 'specific_install' gem
than create a separate project due to this one small feature.

Thoughts?

—
Reply to this email directly or view it on GitHub
#30.

[jdrago999]

I'd be down with that, pull request welcome :)

Great - just curious about the current method of gem installation, vs explicitly shelling out to do it. I assume there is a cross-platform reason for the way it is now.

Care to comment on that?

[rdp]

It appears to just call out to system to build the gem
https://github.com/rdp/specific_install/blob/master/lib/rubygems/commands/specific_install_command.rb#L150
then uses some rubygem command to do the install. I can't remember why.

On Wed, Oct 14, 2015 at 5:35 PM, John Drago notifications@github.com
wrote:

I'd be down with that, pull request welcome :)

Great - just curious about the current method of gem installation, vs
explicitly shelling out to do it. I assume there is a cross-platform reason
for the way it is now.

Care to comment on that?

—
Reply to this email directly or view it on GitHub
#30 (comment)
.