Not all packages included in perl 5.16.0 have a corresponding virtual/perl-* package. This is a little untidy, and in some cases the most recent perl-core/* package is actually older than what's in perl 5.16.0 (assuming version numbers are accurate, and assuming installing such a perl-core package masks what's shipped with perl). Is this just an oversight, or is there something odd about version numbers in packages integrated vs. split out? A few where I'm unsure how they should exist in the tree because the version number in perl is weird: newest perl-ExtUtils-MakeMaker is 6.620.0, perl has 6.63_02 (version number scheme change? 6.620.0 identifies itself as 6.62 internally...) newest perl-File-Spec is 3.330.0, perl has 3.39_02 (version number scheme change?) perl has Module::Build 0.39_01, of which there is no perl-Module-Build equivalent (version number scheme change?) Missing virtuals where I'm reasonably sure about the version number: perl-Compress-Raw-Zlib-2.048 (newest in tree 2.52.0) perl-ExtUtils-CBuilder-0.280.206 (newest in tree 0.280.205) perl-ExtUtils-Install-1.58 (newest in tree 1.54) perl-ExtUtils-Manifest-1.61 (newest in tree 1.600.0) perl-ExtUtils-ParseXS-3.16 (newest in tree 3.150.0) perl-Storable-2.34 (newest in tree 2.350.0) It'd be nice to have these so slightly obsessive-compulsive people like myself can mask virtuals newer than what's in perl to avoid pulling in lots of extra packages. But the packages where what's in perl is newer than what gets pulled in via the virtual seem like they might be bugs (unless I misunderstand how these version numbers work and what's in the tree really is newer despite having a lower version number).
5.16.3 current stable, wont to fix 5.16.0
