On 28/05/08 at 15:33 -0000, Neil Wilson wrote:
> OK.
>
> 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?
For each Debian package where a gem also exists, you would have to
modify the Debian package to use the alternatives system. That clearly
doesn't work.
--
| Lucas Nussbaum
| <email address hidden> http://www.lucas-nussbaum.net/ |
| jabber: <email address hidden> GPG: 1024D/023B3F4F |
On 28/05/08 at 15:33 -0000, Neil Wilson wrote: gems/1. 8/bin'. mongrel_ rails to the gem version. Then we install the apt
> OK.
>
> So patch to gem1.8 to call update-alternatives with a lowish priority
> whenever it fiddles with '/var/lib/
>
> 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/
> 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?
For each Debian package where a gem also exists, you would have to www.lucas- nussbaum. net/ |
modify the Debian package to use the alternatives system. That clearly
doesn't work.
--
| Lucas Nussbaum
| <email address hidden> http://
| jabber: <email address hidden> GPG: 1024D/023B3F4F |