patcon has quit [Remote host closed the connection]
axl_ has quit [Quit: axl_]
havenwood has quit [Remote host closed the connection]
<indirect>
kc8qvp_: bundler is pretty explicit about running sudo
rjhunter has joined #bundler
g0bl1n has quit [Quit: Ex-Chat]
samphippen has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
axl_ has joined #bundler
<kc8qvp_>
indirect: I have mine as nopasswd and it never told me it was running commands as root
axl_ has quit [Quit: axl_]
axl_ has joined #bundler
<pipecloud>
kc8qvp_: Who ever thought using nopasswd was a good idea? :\
<kc8qvp_>
pipecloud: well the same thing would happen if you ran bundler within a few minutes of using sudo for something else
<kc8qvp_>
since that's the default sudo configuration
<pipecloud>
kc8qvp_: Gems can package anything they want. Talk to the author if you think that sudo isn't necessary for what they're trying to accomplich.
<pipecloud>
accomplish*
<kc8qvp_>
what author?
<kc8qvp_>
bundler's author?
<kc8qvp_>
and, you know what
<kc8qvp_>
I've come to realize that it's not gem that's doing it
<kc8qvp_>
it's bundler itself
<kc8qvp_>
it installs packages system-wide by default, despite this being advised against
<kc8qvp_>
and it will run sudo to do so w/o telling you.
<kc8qvp_>
terrible design.
<pipecloud>
Oh that's not bundler's fault. It's installing to your GEM_HOME, which requires root. So it asks for it.
<kc8qvp_>
except it does not ask
<pipecloud>
That's exected. You just use nopasswd, but your argument about the defaults makes some sense.
<pipecloud>
kc8qvp_: It does ask, you just don't get asked because you use nopasswd.
<kc8qvp_>
exactly, so it doesn't ask *me*
<pipecloud>
It requests privilege escalation.
<kc8qvp_>
or even *mention* it
<kc8qvp_>
and I see you realize this affects more than just people who have nopasswd set
<pipecloud>
My rubies and $GEM_HOME are owned by my user.
<pipecloud>
So this never effects me.
<kc8qvp_>
it really should not run sudo w/o saying so
<kc8qvp_>
whether y'all choose to change it or not, I don't care
<pipecloud>
So you'd rather bundler fail and say something about insufficient privileges?
<kc8qvp_>
of course, yes!
<kc8qvp_>
like every other program on my system does!
<kc8qvp_>
haha, wtf
deepender has joined #bundler
<pipecloud>
Not every one does, but most do.
<pipecloud>
kc8qvp_: I'd open an issue with bundler with reproduction steps and as much info as you can provide. Not because this is particularly non-trivial, but it'll get more attention if it's better documented.
kc8qvp_ has left #bundler ["I'll take my trivial concerns elsewhere."]
axl_ has quit [Quit: axl_]
cwebber has joined #bundler
cwebber has quit []
<deepender>
tmoore: there?
cwebber has joined #bundler
cwebber has quit []
rjhunter has quit [Remote host closed the connection]
JordanFaust_ has joined #bundler
JordanFaust_ has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
cha1tanya has joined #bundler
rjhunter has joined #bundler
rjhunter has quit [Ping timeout: 240 seconds]
rjhunter has joined #bundler
rjhunter has quit [Ping timeout: 246 seconds]
rjhunter has joined #bundler
rjhunter has quit [Ping timeout: 240 seconds]
r0bby_ has joined #bundler
robbyoconnor has quit [Read error: Connection reset by peer]
<tmoore>
deepender: I am now
rjhunter has joined #bundler
rjhunter has quit [Ping timeout: 272 seconds]
<deepender>
tmoore: now?
<tmoore>
Yes hi
<pipecloud>
tmoore: Would it be reasonable to open a feature request that has bundler bomb out with permission errors instead of using sudo to install gems?
<tmoore>
I guess that the drawback would be that if you need to install to a directory that's not writable by your user, then you need to run all of Bundler as root and not just the part that installs the gems
<tmoore>
When I said to write specs I meant rspec... the tests for the functionality
<tmoore>
indirect is saying that the messages should be displayed in full if you pass the verbose option, but the code in that pull request doesn't do that
<deepender>
it do that it shows message in full
<deepender>
does it meant that
<deepender>
ohh sorry about spec,I thought you were asking written I am really dumb.
<tmoore>
no worries... I should have clarified
<deepender>
do you mean this: Using uglifier (2.2.1) from /home/deepender/niveshi/bundle/ruby/2.0.0/specifications/uglifier-2.2.1.gemspec