http://search.cpan.org/~tjenness/File-Temp-0.20/ [root@pils ~]# perl -e 'use File::Temp; print "$File::Temp::VERSION\n"' 0.18 [root@pils ~]# cat /etc/redhat-release Fedora release 9 (Sulphur) Either split of File::Temp into a perl-File-Temp package or upgrade the included File::Temp to 0.20. The problem is - for me - mainly MailScanner, which comes with File::Temp 0.20 and has to force the install of a perl-File-Temp-0.20 package. All not so bad, until it comes to update perl-* via yum. Actually it doesn't work. You have to do it manually....
No problem, I can include it in next update.
The reason there is no perl-File-Temp subpackage is because base perl depends on it, specifically: /usr/bin/c2ph /usr/bin/perlbug /usr/bin/pstruct /usr/lib/perl5/5.10.0/Pod/Perldoc.pm /usr/lib/perl5/5.10.0/Test.pm Now, I suppose we could still subpackage it out and have perl depend on the subpackage, but that seems a little... circular. Marcela, I have a patch whipped up locally that updates to 0.20, i'm test building it now.
I was thinking about providing a subpackage from within the perl-package (to provide it for dependencies) and externally provide a newer package (for small footprint updates)? Or would this break createrepo and koji? I'm not sure what happens if two packages provide the same binary RPM, where one is newer... :-) Or just some 'bootstrap' option for the perl.spec?
We're really trying to avoid the "bootstrap" option in the perl spec, bootstrapping a new major perl version is extremely painful as is. The perl package has: Provides: perl-File-Temp = 0.20 Obsoletes: perl-File-Temp < 0.20 That's on top of the automatically provided: perl(File::Temp) = 0.20 It is easy enough to update the version included with base perl, which is what I did.
Well. Easy it is to update the package. But then the user has to download a new perl package (libs, devel, whatever)... That's actually not large, but it's not small either.... Just some thoughts... *I* don't mind bandwidth!
Yes, but perl-File-Temp is not only one subpackage. Perl (core) package includes the main modules often used and many of them were already updated. Yes, it's awful to receive every now and then new update. I'm usually waiting for more problems, which are shipped in monthly update ;-)
Marcela, I didn't push the F-9 update that I built for this reason (it only had this change). If you think we should go ahead and do the update for just this change, I can.
There's previous forgotten perl build in updates testing for a long time, so I do new update also with File::Temp.
perl-5.10.0-38.fc9 has been pushed to the Fedora 9 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update perl'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-8826
perl-5.10.0-38.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.