Package: rbenv Version: 0.1.2+git20100922-1 Severity: wishlist I was kind of hoping that the Debian rbenv package would solve the problems existing with rubygems in Debian. In particular, that it would automatically create and/or use scripts that point to the currently selected Ruby version for the gems installed system-wide.
However, this is what happens: [matijs@...] rbenv global 1.8.7-debian [matijs@...] sudo gem1.8 install bundler [sudo] password for matijs: Successfully installed bundler-1.0.21 1 gem installed [matijs@...] rbenv rehash [matijs@...] which bundle /usr/local/bin/bundle [matijs@...] head -n 1 /usr/local/bin/bundle #!/usr/bin/ruby1.8 [matijs@...] rbenv global 1.9.3-debian [matijs@...] which bundle /usr/local/bin/bundle [matijs@...] head -n 1 /usr/local/bin/bundle #!/usr/bin/ruby1.8 So, executing just bundle will still use ruby 1.8. What I would really like to happen is one of the following: - Bug #637914 is resolved, and rbenv adds the path that is appropriate for the selected Ruby verion to PATH. - rbenv creates shims for any script it finds in /usr/local/bin that starts with a ruby hashbang. A combination of the two is also fine :-). Kind regards, Matijs van Zuijlen -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash 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-2 Versions of packages rbenv recommends: ii ruby1.8 1.8.7.352-2 ii ruby1.9.1 1.9.3.0-2 rbenv suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
