Joseph Method <[EMAIL PROTECTED]> wrote: > The argument for the second is that gem binaries could then supercede system binaries. We need to clarify whether this is really beyond the pale, since the decision to install a gem is an administrator decision, not a user decision. In other words, installing a gem is equivalent to installing a source package except that gems allow for quick uninstall.
Almost. It's the Gem and whatever else the Gem needs. Personally, I see no problem with installing a Gem that an adminstrator explicitly asks to have installed in the system path. My primary concern is with the dependencies Gems pull in with them. If this is largely beyond the scope of Debian policy, then such 'packages' have an obligation to not cause problems for packages using the system packages. -- Add rubygems bin to PATH https://bugs.launchpad.net/bugs/145267 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
