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?

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.


In reply to Re^4: Testing for non-perl system requirements by leocharre
in thread Testing for non-perl system requirements by leocharre

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.