supercoven has quit [Read error: Connection reset by peer]
jenrzzz has joined #ruby
supercoven has joined #ruby
TrufflePump has joined #ruby
jenrzzz has quit [Ping timeout: 240 seconds]
TrufflePump has quit [Ping timeout: 258 seconds]
Fernando-Basso has quit [Remote host closed the connection]
Fernando-Basso has joined #ruby
jenrzzz has joined #ruby
TCZ has quit [Quit: ...]
jla has joined #ruby
jenrzzz has quit [Ping timeout: 252 seconds]
Fernando-Basso has quit [Quit: May the force]
TrufflePump has joined #ruby
brigitte has joined #ruby
aloy has quit [Ping timeout: 260 seconds]
TrufflePump has quit [Ping timeout: 258 seconds]
sgen has quit [Remote host closed the connection]
sgen has joined #ruby
TrufflePump has joined #ruby
jenrzzz has joined #ruby
jenrzzz has quit [Ping timeout: 246 seconds]
Technodrome has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
yuesbeez has joined #ruby
evdubs_ has joined #ruby
jenrzzz has joined #ruby
evdubs has quit [Ping timeout: 240 seconds]
TorpedoSkyline has quit [Quit: Konversation terminated!]
nixue has joined #ruby
jenrzzz has quit [Ping timeout: 240 seconds]
work_ has joined #ruby
feriman has joined #ruby
jenrzzz has joined #ruby
jenrzzz has quit [Ping timeout: 240 seconds]
cow[moo] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
TrufflePump has quit [Ping timeout: 258 seconds]
cow[moo] has joined #ruby
robotbee has joined #ruby
Technodrome has joined #ruby
jla has quit [Ping timeout: 246 seconds]
sagax has quit [Quit: Konversation terminated!]
moldorcoder7 has quit [Ping timeout: 252 seconds]
c355e3b has quit [Changing host]
c355e3b has joined #ruby
moldorcoder7 has joined #ruby
jenrzzz has joined #ruby
jenrzzz has quit [Ping timeout: 268 seconds]
<yuesbeez>
does gem update conflict with bundler? how does gem update handle bundler gems on a specific version?
<jhass>
not sure but given multiple versions of the same gem can be installed I'd guess worst case the next bundle install will reinstall the needed version
<yuesbeez>
jhass: so they would conflict with each other though? Is there any way for bundler to keep specific versions of a gem installed and also keep the latest version installed?
<jhass>
what does conflict even mean here?
<jhass>
so actually doing as much as gem help update:
<jhass>
> The update command does not remove the previous version. Use the cleanup
<jhass>
command to remove old versions.
<yuesbeez>
that bundler is keeping a few older versions of a gem installed and gem update will update them all to the same latest version
<yuesbeez>
I see so by default gem update will instal the newer version alongside the old version?
<jhass>
that's what the command description I copy pasted you above from gem help update says, no?
<jhass>
do you have an actual problem?
jla has joined #ruby
FastJack has joined #ruby
MalkbabY_ has joined #ruby
DTZUZU has quit [Read error: Connection reset by peer]
<yuesbeez>
Just trying to understand what these tools are for. So essentially if I wanted to install multiple versions of a gem on a set of machines I can do that with gem install. But if I want to manage which version of gems are used in different projects thats what bundler is for
<jhass>
bundler also makes it easy to install those specific versions
<jhass>
with --path to a local site dir too
<jhass>
it uses rubygems behind the scenes to that that job
<jhass>
eh, to do that job
<yuesbeez>
What I need to do is manage the gem installed for all users on hundreds of macs. So this isnt for my own development use
<yuesbeez>
It seems like bundler would be the wrong tool for that
MalkbabY has quit [Ping timeout: 240 seconds]
<jhass>
probably yes, I think some stuff is packaged in homebrew too but using gem directly seems fine
<yuesbeez>
Thanks for the info. The gems themselves are needed on the machines for development though so that seems to be if I wanted to install an app already built
<jhass>
if it's developer machines why not let the developers set up their machines themselves to their liking?
<yuesbeez>
Theyre developers-in-training so setting up the environment is sort of my problem
<jhass>
write good documentation and let following that be the first training?
<yuesbeez>
Yes I will write some documentation especially for bundler as it seems they could install gems themselves without admin access
<jhass>
mainly that it becomes part of your brew update / brew cleanup cycle
<yuesbeez>
I see, thanks for finding that I didnt think to check that. And I can install ruby using homebrew system wide without issues right? And it will share the same gems as system ruby
<jhass>
uh, I never really checked what that does, I wouldn't be surprised if homebrew ruby is keg only
<yuesbeez>
So installing ruby with homebrew would conflict with system ruby as well right? Since setting the system up for homebrew ruby would change the dependency links
mozzarella has joined #ruby
<jhass>
keg only means it's not in any lookup paths unless explicitly put there
<jhass>
not sure why you'd install it in the first place if you're fine with system ruby though
<yuesbeez>
Supporting the system ruby seems easiest. And then users could install ruby themselves if they need a specific version to their local user right?
<jhass>
right, that's what we got rvm, rbenv or chruby for
TrufflePump has joined #ruby
<yuesbeez>
Can they do that without admin access though? I read rvm really messes with the system
<yuesbeez>
Im assuming they have an alternative local user mode of some sort
<jhass>
rvm and rbenv recommend a user install by default, you need to do extra effort to do the system installation
<jhass>
chruby is easy to install per user too, it's essentially just 100 lines of shellscript to source
<yuesbeez>
Also does the n flag change the default behavior at all if by default it doesnt uninstall any gems?
<jhass>
I think this might get faster if you just try out a couple of things and go by the assumption that stuff works. Nobody here is a computer and can dry run your shell script for you ;)
<yuesbeez>
Im just trying to understand the documentation. If you dont know the answer off hand thats understandable. I was misreading as the -n option is an option for gem cleanup and install. For install it is "Directory where executables will be placed when the gem is installed"
TrufflePump has quit [Ping timeout: 258 seconds]
<yuesbeez>
jhass: thank you so much for your help
<jhass>
yw :)
<weaksauce>
+1 for ruby_install and chruby
<weaksauce>
local install your rubies
duderonomy has joined #ruby
work_ has quit [Quit: Connection closed for inactivity]
TrufflePump has joined #ruby
lockweel has quit [Quit: Leaving]
prestorium has quit [Ping timeout: 245 seconds]
prestorium has joined #ruby
prestorium has quit [Read error: Connection reset by peer]