I'll try out PAR when I have enough time to give it a good grok. It may not be the best fit for this project, but it would be an interesting thing to have in the toolbox.

But how is a Pure Perl version of Module::X going to make that any easier?

The Pure Perl versions have an advantage, since you can just bundle them up in a download with, say, (in my case) a webapp that requires it. I can't really do that with an XS module.

Of course now, since I'm not using CPAN, all the package goodness is out the window. I'm hoping to move this particular app into a mode where you can install it via `make; make test; make install` if you want (using Module::Install) and if you don't know how to do that, you can just download a prepackaged deal. Currently, you're only choice *is* the prepackaged deal. Popular with end-users, not so elegant when looked at by Perl Hackers. What to do?

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.