Currently playing around with Andreas König's Perl::Repository::APC which is extremely cool when one has arranged for a few things in beforehand.
So far my way of working with the Perl core has been rather cumbersome. I do have rsynced the blead- and maint-branch which is ok when preparing a patch. However, it is not enough when trying to track down what the effects of a particular patch are. So I tried it with patchaperlup first which - according to its documentation - should be able to create a Perl source-directory up to a given change from an existing source-tree and a directory of patches. However, that didn't work.
So I looked into buildaperl. To my dismay I read that I need to have a full rsync mirror of the APC so I rsynced one and now have almost 700 new megabyte in my home-directory. The good thing is that it works and it took me around two minutes to create perl-p-5.8.0@21751 with it. Very nice.
And now I'll indulge with perlbench a little.
Repository (Score:3, Interesting)
Reply to This
Re:Repository (Score:2, Informative)
Right now I am getting most of the stuff I want to know from the perlbrowse repository [activestate.com]. After you improved some bits of it some while ago it's really useful and (most importantly in my case;-) easy to use.