Comment 49 for bug 145267

Revision history for this message
Neil Wilson (neil-aldur) wrote : Re: [Bug 145267] Re: Add rubygems bin to PATH

2008/8/14 Lucas Nussbaum <email address hidden>:
> Hi,
>
> Some comments:
> - debian/operating_system.rb is not properly licensed, and not mentioned in debian/copyright.

Agreed. That needs some tidying up. I can't see any copyright message
in there about the debian packaging either. Does Debian need that as
well?

> - I'm still not convinced by your update-alternatives hack. This should *really* go upstream, so it's fixed for every distro, not just Ubuntu.

It will do Lucas, but that won't happen in the week I have before
feature freeze. Please consider this a pragmatic prototype.

> - why the switch to simple-patchsys?

That's easy - it's simpler :-). cdbs-edit-patch is the bees knees. No
longer do I hate patching.

> - you base your version on a git snapshot, with a >5kloc diff compared to the current version in debian unstable. Is that really reasonable, since we are far in the Ubuntu release cycle AFAIK?

I have it on good authority that the version in Debian may very well
be out of date by the end of the month. ;-)

> - have you talked to Daigo Moriwaki about those deep changes to his Debian package? If not, when do you plan to?

At the moment Debian bug #403407 is still marked "won't fix" so there
is clearly going to be a divergence whatever happens. You really need
to alter the bug status if Debian is serious about fixing the path
problem.

I'd be more than happy to sync up with the excellent work Daigo has
done on his package, but they're never going to be the same until
Debian accepts that the problem is fixable.

Can you do something about that?

> - You never answered by question about a bug# in https://bugs.launchpad.net/ubuntu/+source/libgems-ruby/+bug/145267/comments/42 .

Could you help and file one? Otherwise Debian will have to wait. I'm
kinda busy with a FeatureFreeze deadline and my real job.

> If I understand it correctly, you want to give Ubuntu a competitive
> advantage by not working with upstream to address this problem globally.
> That doesn't sound right.

Yes I suppose you probably see it that way. I can't help you with that
and I don't understand why you would want to adopt such a viewpoint.

I'll let the rubygems commit logs, bug tracker and mailing list speak
for whether I work with upstream or not.

--
Neil Wilson