Comment 8 for bug 145267

I'll clarify that. The issue with sudo is that it sets its path to to a SECURE_PATH setting for security purposes. Nothing outside of those directories will be run by sudo by default. That is as it should be.

Unfortunately that means anything installed by 'gem' cannot be run directly by sudo without specifying the full path.

That is known as 'syntactic vinegar' and hopefully it will irritate somebody sufficiently to package the gem properly :-)