Your message dated Wed, 30 Nov 2011 21:33:02 -0200
with message-id <[email protected]>
and subject line Re: [DRE-maint] Bug#649775: rbenv: Does not work with non-root
installed gems
has caused the Debian Bug report #649775,
regarding rbenv: Does not work with non-root installed gems
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
649775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649775
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rbenv
Version: 0.1.2+git20100922-1
Severity: normal
Dear Maintainer,
I prefer not to install gems as root, e.g.
$ gem install passenger --user-install
rbenv doesn't seem to create shims for user-installed binaries
$ rbenv which passenger-install-nginx-module
rbenv: passenger-install-nginx-module: command not found
is this expected behavior? is there a workaround?
Thanks
Brandon
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.0.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages rbenv depends on:
ii ruby 4.8
ii ruby1.8 [ruby-interpreter] 1.8.7.352-2
ii ruby1.9.1 [ruby-interpreter] 1.9.3.0-1
Versions of packages rbenv recommends:
ii ruby1.8 1.8.7.352-2
ii ruby1.9.1 1.9.3.0-1
rbenv suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Brandon Simmons escreveu isso aí:
> > For now, you can workaround this doing what I do, which is using `gem
> > install --user-install` plus something like this on my .bashrc:
> >
> > eval "$(rbenv init -)"
> > # [...]
> > if which ruby >/dev/null && which gem >/dev/null; then
> > PATH="$(ruby -rubygems -e 'puts Gem.user_dir')/bin:$PATH"
> > fi
>
> This is a fine solution for me, thanks. I think I have a better idea
> of what all the moving parts are doing now. Could this note make it
> into the README.debian? Also, for zsh users I put the lines above into
> my ~/.zshenv file.
I guess this is not an issue specific to Debian and neither to rbenv.
Even with plain RubyGems, if you use --user-install you will need to set
the $PATH on your own. I've just submitted a small text about this for
the FAQ section of the RubyGems Guides site:
https://github.com/rubygems/guides/pull/14
I am closing this bug.
Thanks.
--
Antonio Terceiro <[email protected]>
signature.asc
Description: Digital signature
--- End Message ---
_______________________________________________
Pkg-ruby-extras-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ruby-extras-maintainers
