Comment 26 for bug 145267

On 28/05/08 at 19:21 -0000, Neil Wilson wrote:
> On 28/05/2008, Lucas Nussbaum <email address hidden> wrote:
> > 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.
>
> Why not?

Take a given Debian package. How will you determine if this package
might be coinstalled with a gem providing the same binary at some point?

Will you just ask all packages providing ruby apps with executables to
switch to the alternatives system?

> Surely that should be part of the packaging wrapper for a package that
> is also a rubygem and which generates executables. (which would
> include putting the appropriate data files in the gem data area to
> tell gem that the facility is installed so that gem dependencies work
> correctly).

How do you deal with non-ruby packages having the same name as a binary
from a gem? Name clashes will happen for sure.

> It's all about making the debian packages co-operate with gem. They
> can co-operate through the alternatives system and avoid standing on
> each others toes.

That really doesn't seem like a possible solution to me. It's also too
complicated for users: most users don't know anything about the
alternatives system.
--
| Lucas Nussbaum
| <email address hidden> http://www.lucas-nussbaum.net/ |
| jabber: <email address hidden> GPG: 1024D/023B3F4F |