Bundlers shows root warning on Windows

[luislavena]

Environment information:

• ruby 2.0.0p451 (2014-02-24) [x64-mingw32]
• Bundler version 1.6.2

It shows the following warning when using on Windows:

Don't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.

Bundler uses Process.uid to determine if current process is run by root, but the problem is Ruby on Windows Process.uid always return 0:

C:\Users\Luis>ruby -ve "p Process.gid"
ruby 2.0.0p451 (2014-02-24) [x64-mingw32]
0

Independently of the current user.

I believe an extra check about the platform will be enough to avoid this warning.

[indirect]

oh no :( thanks for letting us know!

On Tue, Apr 15, 2014 at 5:39 PM, Luis Lavena [email protected]
wrote:

Environment information:

• ruby 2.0.0p451 (2014-02-24) [x64-mingw32]
• Bundler version 1.6.2
  It shows the following warning when using on Windows:

Don't run Bundler as root. Bundler can ask for sudo if it is needed, and
installing your bundle as root will break this application for all non-root
users on this machine.

Bundler uses Process.uid to determine if current process is run by root, but the problem is Ruby on Windows Process.uid always return 0:

C:\Users\Luis>ruby -ve "p Process.gid"
ruby 2.0.0p451 (2014-02-24) [x64-mingw32]
0

Independently of the current user.

I believe an extra check about the platform will be enough to avoid this warning.

Reply to this email directly or view it on GitHub:
#2984

[luislavena]

@indirect thank you! ❤️ ❤️ ❤️

[andregriffin]

Why does 1.6.3 not show up anywhere? gem install still uses 1.6.2 on windows.

[luislavena]

@andregriffin there is no 1.6.3 tag or release or yanked gem.

[indirect]

We haven’t actually released it yet. 😳 I’ll try to do it tonight!

On May 20, 2014, at 10:29 PM, Luis Lavena [email protected] wrote:

@andregriffin there is no 1.6.3 tag or release or yanked gem.

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

[andregriffin]

Ah, no worries. I must have forgotten that I manually added this commit this in my last env, and saw the changelog this time and thought I was missing something. Thanks!