[DRE-maint] sponsorship for libfastthread-ruby
Gunnar Wolf
gwolf at gwolf.org
Wed Mar 26 22:20:33 UTC 2008
Micah Anderson dijo [Tue, Mar 25, 2008 at 04:24:00PM -0400]:
> > 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?
If it is the case, indeer, you are right. However, this is quite
common to do in Perl-land - Perl has a very large set of core
libraries (perl-modules) but is not updated all that often. The
modules themselves keep evolving. Thus, we often see a certain core
module being independently packaged.
Of course, whenever a new Perl version hits the streets, those modules
have to be checked for updatedness, so they are at least at the same
version as Perl itself. Otherwise, as (for this very reason)
individual modules have precedence over core modules, we'd only be
installing regressions.
Greetings,
--
Gunnar Wolf - gwolf at gwolf.org - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF
More information about the Pkg-ruby-extras-maintainers
mailing list