in reply to Packaging programs (as opposed to modules)

It sounds like you're trying to distribute a web application. You might be interested in reading this: Installation System Design for a Large Apache/mod_perl Application. The design described there is being used, with some modifications, in Krang. So far it's worked very well for us.

-sam

  • Comment on Re: Packaging programs (as opposed to modules)

Replies are listed 'Best First'.
Re: Re: Packaging programs (as opposed to modules)
by u235sentinel (Hermit) on Apr 16, 2004 at 16:11 UTC
    Forgive my ignorance but I thought a package was a module. Is this not the case?

    I am reading through Oreilly's "Perl Objects, References and Modules". There was a chapter which discussed "Packages". It sounded like a regular module. Or am I just not getting it? Thx

      "Packaging" in this sense is putting together a set of application-level scripts, configuration files, etc. in a form suitable for distribution and installation. In other words, I am using the word "package" in one of its common English senses and not in its Perl sense.

      If I'm not mistaken, in Perl (5), every module is a package, but not every package is a module. The "package" keyword simply defines a non-default name space in which to put variables, functions, and/or methods. It can be used within an ordinary script, but is usually used at the top of a module's .pm file to define the name space of the module using the module's name.