[DRE-maint] sponsorship for libfastthread-ruby

[Micah Anderson]

* Matt Zagrabelny <mzagrabe at d.umn.edu> [2008-03-25 10:43-0400]:
> 
> On Tue, 2008-03-25 at 13:02 -0400, Micah Anderson wrote:
> > * Matt Zagrabelny <mzagrabe at d.umn.edu> [2008-03-25 09:22-0400]:
> > > Greetings,
> > > 
> > > I have packaged up fastthread for ruby in package libfastthread-ruby. It
> > > is lintian clean and is a pretty small package (one .so to install.) I
> > > have packaged it up in preparation for packaging capistrano (either
> > > myself or the person who filed #428879).
> > > 
> > > I am wondering if anyone would be willing to sponsor the upload?

I may sponsor it, but first please see below.

> > Have you seen this thread:
> > http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2007-December/001865.html
> > 
> > which was thread hijacked, and then resumed here:
> > http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/2007-December/001946.html
> > 
> > Specifically, I packaged this already, but then removed it from the svn
> > repository because it turned out that fastthread was merged into ruby
> > 1.8.6, and AFAICT since ruby 1.8.6 there is no use for this library
> > anymore.
> 
> > However, maybe you have a justification that I am not aware of?
> 
> Two issues still exist:
> 
> 1) Capistrano complains that fastthread is not installed. Perhaps a bug
> could be filed against Capistrano.

I think that this is the right way.

> 2) The following email snippet was taken off of ruby-talk google group:
> 
> http://groups.google.com/group/ruby-talk-google/browse_thread/thread/7933e7e987dad1c3

Thanks for finding this, this is interesting information.

It strikes me as odd that libfastthread needs to be released to fix this
problem, rather than the problem is fixed in ruby itself. I suppose
there may be a delay in the release of a new version of ruby that would
have this fix? If so, have you looked at maybe taking those fixes and
applying them to the debian ruby package? It seems a little silly to
have a package for a short period of time to fix this bug, and then have
to remove it again. Like will this be fixed in ruby in a month, two
months? Before Lenny releases?

Again, you may be aware of more than I am about this situation, and
I'm interested to know. If it still does make sense to package
libfastthread, I'd be happy to sponsor it (although it would be nice to
know if the version I packaged has anything to offer to yours).

Micah