Closed kneath closed 13 years ago
If you're using homebrew, you're most certainly know what sudo is.
Let's say I'm a HTML/CSS guy who haven't written any Ruby code. I have no idea what gem
and sudo
are. I use Mac OS X 10.6 that ships with Ruby in /usr/bin/ruby.
$ gem install livereload WARNING: Installing to ~/.gem since /Library/Ruby/Gems/1.8 and /usr/bin aren't both writable. WARNING: You don't have /Users/nv/.gem/ruby/1.8/bin in your PATH, gem executables will not run. Successfully installed livereload-1.4 1 gem installed Installing ri documentation for livereload-1.4... Installing RDoc documentation for livereload-1.4... $ livereload -bash: livereload: command not found
It doesn't work! I have to idea what's going on. How would I know what I have to either add PATH=$PATH:$HOME/.gem/ruby/1.8/bin
into my .profile or run sudo gem install livereload
?
NV: +1
kneath: sorry, you made a good point, but the Ruby community is not ready yet to give up sudo out of the box. Closing this ticket.
I modified the README to better cooperate with modern gem management. If you are using a tool like homebrew, or installing gems in your home directory, there's no need for sudo. If you require sudo, you can still add it on — but in general the ruby community is moving away from this approach.
I also removed the gem update calls, as I couldn't see any reason they were listed there...