Let me start with apologies to any one out there that is both reading my feed and waiting on me for their favoritest bug to be resolved – been a bit swamped back in reality, making G time short the last few days. I hear your cries and will be picking up tissue for you on my way home tonight, promise.
On the perl qa effort of mine, there I have a bit of progress, thanks to hours I didn’t have to write/debug code and a decent machine to run it on. I’ve had a real problem locating a list of the modules and versions that come with a core perl install – so I built a chroot, and did a lot of install/wipe/install to produce this list for perl 5.8.2, 5.8.4, 5.8.5, and 5.8.6, mapping out which modules and module versions come with each gentoo supported release.
But wait, there’s more! That’s right, not satisfied with just this list, I did some bash foo so I could extract P/MY_P, PV/MY_PV, etc., from the tree of gentoo perl module ebuilds (probably an easier method than my madness, but that was the easy part of this process) which allowed me to produce this listing of those perl modules that are both installed in a core perl install and have an ebuild in portage. The output could probably use some reworking so that it’s easier to see which arch is in the clear and which one needs bumping, as well as which modules don’t have current ebuilds compaired to the perl core install, but all that in time children. At least it’s a visual map that makes sense to me.
And that’s it for my little world right now. I realize that with perl being involved (cc, assigned, etc.) with about 130 bugs right now, that this little qa tirade of mine might seem a waste, but I really believe that this is for the better in the long term.