So patch to gem1.8 to call update-alternatives with a lowish priority
whenever it fiddles with '/var/lib/gems/1.8/bin'.
Similarly to gem1.9.
Now what about the corresponding apt-package. Let's say we have
'mongrel' installed via gems with the alternatives system pointing
/usr/bin/mongrel_rails to the gem version. Then we install the apt
package and there is a name clash. If something has been packaged that
is also a ruby gem how do we do the naming for the binaries?
2008/5/28 Rocco Stanzione <email address hidden>:
> Now that's not a bad idea. I hadn't thought of using the alternatives
> system.
>
> --
> Add rubygems bin to PATH
> https://bugs.launchpad.net/bugs/145267
> You received this bug notification because you are a direct subscriber
> of the bug.
>
OK.
So patch to gem1.8 to call update-alternatives with a lowish priority gems/1. 8/bin'.
whenever it fiddles with '/var/lib/
Similarly to gem1.9.
Now what about the corresponding apt-package. Let's say we have mongrel_ rails to the gem version. Then we install the apt
'mongrel' installed via gems with the alternatives system pointing
/usr/bin/
package and there is a name clash. If something has been packaged that
is also a ruby gem how do we do the naming for the binaries?
2008/5/28 Rocco Stanzione <email address hidden>: /bugs.launchpad .net/bugs/ 145267
> Now that's not a bad idea. I hadn't thought of using the alternatives
> system.
>
> --
> Add rubygems bin to PATH
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Neil Wilson