Can we nix the personal attacks please. I don't know what policy, if any, is responsible for this, but as far as I can tell no other package installs files in /usr/local/bin, and I don't think they should. See the FHS: http://www.pathname.com/fhs/pub/fhs-2.3.html#USRLOCALLOCALHIERARCHY
I figure there are 3 reasonable options, which could be checked against the packaging policies:
* Install executables in /usr/bin
* Add the gem bin path to $PATH
* Install symlinks in /usr/bin
I don't think the reasonable-results argument against modifying $PATH is a very strong one, but that's still not my favorite solution. The fewer places my shell has to look when I run a command, the happier I am. Rubygems are sort of a special case, where maybe the policies didn't anticipate certain needs. Maybe a policy exception needs to be made, or maybe a new policy.
Can we nix the personal attacks please. I don't know what policy, if any, is responsible for this, but as far as I can tell no other package installs files in /usr/local/bin, and I don't think they should. See the FHS: www.pathname. com/fhs/ pub/fhs- 2.3.html# USRLOCALLOCALHI ERARCHY
http://
I figure there are 3 reasonable options, which could be checked against the packaging policies:
* Install executables in /usr/bin
* Add the gem bin path to $PATH
* Install symlinks in /usr/bin
I don't think the reasonable-results argument against modifying $PATH is a very strong one, but that's still not my favorite solution. The fewer places my shell has to look when I run a command, the happier I am. Rubygems are sort of a special case, where maybe the policies didn't anticipate certain needs. Maybe a policy exception needs to be made, or maybe a new policy.