in reply to Re: developing and distributing perl apps
in thread developing and distributing perl apps

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:

Thanks,
techy

  • Comment on Re: Re: developing and distributing perl apps

Replies are listed 'Best First'.
Re: Re: Re: developing and distributing perl apps
by rdfield (Priest) on Feb 26, 2004 at 15:25 UTC
    Nathan? Is that you? :)

    Script reload still doesn't happen under Apache 1.3.x on Win32, but the module reload is working fine now. I haven't tested 0.30 under Apache 2.0 yet.

    rdfield

      rdfield,

      Yes, its me, always looking for a chance to put in a plug for Apache::PAR :-)

      I will take a look at reloading scripts under Win32. Does this happen with both Apache::PAR::Registry and Apache::PAR::PerlRun? Trying Apache 2/mod_perl 2 may be a good idea - Apache::PAR uses a very different system for running Registry/PerlRun scripts under it. In the mean time, if it is appropriate for your application you may also want to try ##UNPACKDIR## in your web.conf and using normal Apache::Registry or Apache::PerlRun config to execute the scripts, as there is also a mechanism for reloading the unpacked content for changed archives.

      Also, I suggest we take this offline as this is slightly OT for this discussion. Can you send me an email with the details?

      Thanks,
      techy (Nathan)