I looked into do that too but found it more of pain than anything. I kept running into annoying differences and various things that just didn't work. One of the main kickers was there I needed module versions that where no longer listed on CPAN.

What I did wasn't any easier though. I ended up writing a script that extract, patch, build, test, and install a list of modules feed to it by a xml file.

I used system calls to handle all the operations on the modules. Cross platform was easy since I used GNUWin32 builds of tar, gzip, patch, and unzip.

In the xml file I would define the modules I wanted to use. Each module had their version, module prereqs, filename of the tar.gz file, and which platform to use it on (sometimes a version A works better on windows than version B which works great on linux). A few modules even needed to have environment variables defined and then post build instructions to copy dlls to arch/auto.

I spent about a week on it, but most of the time was testing and adding little improvements here and there for it. It really makes life simple since all I have to do to support a new module is add it to the xml file and drop the .tar.gz file into a sub directory. In the end it was around 1000 lines, but I do use a lot of whitespace.

I'm not sure if I will get to make it public, but it wasn't that much effort to write it up and I bet a couple of people looking at it can make it pretty solid too.