Although probably not a useful solution for your situation, one neat way around this problem is to create your own mini-CPAN that just contains the modules you need.

That might be a good idea. I need to figrue out if it has enough added value versus a directory of tar-balls to be worth the effort.

You might want to look at Apache Toolbox as a starting point.

Thanks, I hadn't seen that before. Definitely worth a look.

Documenting a standard mechanism for the user of your application to rebuild with the latest module / apache / whatever if necessary.

Definitely on the todo list. I'll probably do this as part of the specification process for the new system.

-sam

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.