Bug 170944 - perl-Set-IntSpan-1.08?
Summary: perl-Set-IntSpan-1.08?
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Set-IntSpan
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ville Skyttä
QA Contact: Fedora Extras Quality Assurance
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2005-10-16 03:14 UTC by Ralf Corsepius
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2005-10-16 18:07:39 UTC

Attachments (Terms of Use)

Description Ralf Corsepius 2005-10-16 03:14:53 UTC
Description of problem:

FE ships perl-Set-IntSpan-1.07 (according to CPAN originating from 1998), though
Set-IntSpan-1.08 had been released May 2004.

Any particular reason for doing so?

Comment 1 Ville Skyttä 2005-10-16 06:31:31 UTC
An oversight, thanks for pointing it out.   BTW, this package could use a new 
maintainer, would you be interested? 

Comment 2 Ralf Corsepius 2005-10-16 06:51:32 UTC
(In reply to comment #1)
> BTW, this package could use a new 
> maintainer, would you be interested? 
Well, the number of packages, I maintain already is close to exceed the number
of modules I feel able to handle. AFAIS, you and other (esp. perl-package)
maintainers are in a similar position.

So, instead of "shifting ownerships" and trying to "stake claims", I am in favor
of teaming up and collaborative maintainership.

In this particular case, this would mean: I don't have a problem in modernizing
the spec and updating the package, but I am not interesting in "long term

Comment 3 Ville Skyttä 2005-10-16 07:01:12 UTC
Yep, that's right.  But this case is a bit special, I no longer really use 
Set::IntSpan anywhere else than the 0.7 branch of w3c-markup-validator, and 
all development of it has moved forwards, and the development version doesn't 
use this module. 
Anyway, I've already updated and cleaned up this in CVS, will build as soon as 
the buildsys feels better again. 

Comment 4 Ville Skyttä 2005-10-16 18:07:39 UTC
1.08-1 built for FC-4 and devel 

Note You need to log in before you can comment on or make changes to this bug.