rdfield,

You can add a PAR file to a mod_perl configuration via the Apache::PAR module. Apache::PAR is written for exactly these kinds of situations.

Dependency checking is probably best avoided by packaging all dependent modules into the PAR file. If this isn't possible, there are a couple of other ways I think dependency checking could probably also be handled:

• Make the PAR file an executable with pp and have the main script check dependencies. That way, a user could run the par file to check dependencies, but still install it on mod_perl using Apache::PAR (untested)
• Using Apache::PAR, add code to the web.conf file in the PAR file using a <PERL></PERL> section which checks dependencies, and prints warnings or errors out as appropriate. Of course, this couldn't check for the existance of Apache, mod_perl, PAR or Apache::PAR, as these are prereqs for loading a web.conf

Thanks,
techy

---

---

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.