I have an app (VCP) that likes to use Pod::Usage to emit help and that likes to allow access to help topics by scanning @INC for modules and .pod files that contain the docs. It also uses the POD in the modules to insert comments in config files it emits for all the options it places in there.
PAR plays subtle and efficient tricks using [EMAIL PROTECTED], but this breaks code like mine. Is there a strategy for generating executables that allows normal @INC behavior using a temp lib directory or some such? Thanks, Barrie
