Sometimes doing it better is using the tools provided.

In this case, the Alien idea is not stupid, without merit, etc. Some of the concepts simply wreak of things that would better reside in rpm/src/makefile land, downloadable packages.

I believe in checking for missing non-perl dependencies/ operating system/ weather conditions, before installing perl modules.
I believe in scripting hacks to install non-perl dependencies.
Creating a standardized perl solution to installing things that are very particular about other dependencies and portability in general.. Could be a tremendous waste of time.
So, my way of doing some of these things better is to not do it.

Take for example Alien::CodePress. It installs something for a website.
Who would make use of this to install javascript and html ona website?

• A user with a shared hosting account?
  What are the chances that Alien::CodePress is already available in the system? She is going to what, install the module, write a script that uses it- all to install html and js files on a website???? Good excercise- but that's all it is.
• Someone with a dedicated server?
  Really? You think so? Instead of wget and tar?????
• A sys admin to managed hosting accounts
  Here's a good chance for usage. Maybe they would offer users through a control panel to install CodePress to a managed hosting account.
  Chances are they have a bash/perl script of their own to do their dirty work. Maybe one they slightly modified from the version that took care of awstats or some other.

Don't get me wrong, I love what they are doing. Go for it. I will stand behind the developers and cheer as they code and debug their little fingers to the bone.
Just as I have.
Even if you reach a dead end (and I've had oodles), you learn- you earn a greater respect and fascination for your peers and beyond, who are creating amazing things and sharing it with the rest of us all.