If the components are represented by individual modules (that may pull in other stuff as required), then you could use a configuration file (or GUI front end) to select the components for a distribution, create a dummy script that uses each of the required components' modules and aim a dependency walker at that to get your manifest.
Once you have a manifest you can either build the makefile.pl, or you could use the manifest and a script to create the directory structure containing the files for distribution. Creating a distribution set of files probably allows easier testing and management of each deployment, although you probably don't want to perform maintenance work on the distribution image.
Perl is environmentally friendly - it saves trees
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||