I'm guessing that there are such things as core modules in a perl distribution to provide...

• A stand-alone useable installation (once compiled & installed) - providing a far simpler introduction since the intending user wouldn't have to download & install the perl compiler/toolset and then subsequently download & install modules - some of which may not work with the (version of the) toolset
• To provide a baseline of the above in order that the usability can, as far as humanly possible, be guaranteed and maintained with the distributed modules

Recently I worked on a Solaris project (which uses ABI standard packaging) where I/we designed

1. A package for the distribution plus a package each for the non-core modules
2. A build process that downloads and translates the perl distribution (& modules) into packages for subsequent deployment and installation onto the target

Or, put another way, designed our packaging to supplement, not ignore, the significant benefits of perl & the CPAN - why re-invent the wheel when perl/CPAN already has the majority of dependency tracking etc. implemented, all you need do is supplement the given dependencies where dependencies may be missing in the original.

---

---

• 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.