You mean, I should write code to do an Automated module install? Part one was "easy" (only took me about 10 hours so far to code and test on Linux, AIX, Windows). Part two, the part I was referring to above, is something I'm not even really sure where to start. Determining what the external dependancy is, programmatically, is not something I'm looking forward to. Figuring out dynamically that XML::Parser requires expat (and then automatically finding it), while figuring out that Crypt::SSL requires OpenSLL (and then automatically finding it), and any other module I may need to distribute ... that's not going to be fun.

More likely is that I figure out my own dependancies by hand, then manually acquire the source/binaries, and then write code that handles that instead. It's not hard, it's just work.

Note that dynamically figuring out that XML::Twig required XML::Parser was painful enough - I'm not sure I want to go through it again for the external libraries ;-) This was due to Makefile.PL-based modules and Build.PL-based modules wanting to do everything differently. And I didn't really want to start parsing perl - perl itself has a hard enough time doing that, and I'm not nearly smart enough to write code to do it. So I kick off the .PL script and parse the output (which is why I had to work out why opening '-|' on Windows wasn't working).

I'm not linking to my old articles for people to vote on them. I'm linking to them to show that I'm already trotting down the proffered road and encountering issues which I really hoped I wouldn't.