in reply to Perl application packaging

There's some discussion of this here.

Replies are listed 'Best First'.
Re^2: Perl application packaging
by bibliophile (Prior) on Jan 26, 2005 at 17:03 UTC
    Interesting, thanks... I'm looking more for information/opinions on how to package up a Perl-based application, rather than how Perl itself is packaged (unless that's the same thing? As I said, new territory for me....)

    I'm assuming that the machine the app will be installed on already has Perl :-)

[reply]

      Probably more intesting than the node I linked to above is the follow-ups (eg. this one for debian systems). There's good info on how to install specfic versions of CPAN modules.

      If you're more worried about your custom (non-CPAN) modues, then CVS or similar may be an option. Good use of tags and branches makes it easy to keep code consistent across multiple systems.

      But it really depends on:

      1. What platform you're running on.
      2. What you're deploying to (eg. servers, desktops, random users on the web)
      3. And maybe how you want to handle CPAN packages.
[reply]
        The app currently runs on either Linux or Windows, with either a local or remote database back-end (which is either PostgreSQL or MySQL).

        I've got all the component Perl modules gzipped (using 'make dist' in each module's own development sandbox).

        Right now, I have to (for example) burn all of the needed modules (my custom ones, and a bunch from CPAN) to CD, copy them to the new system, and then manually make/make test/make install each of them, in a certain order.

        I was going to just write a script to do this, but then thought that there might be a better / canonical way of packaging and installing Perl applications. :-)

[reply]

In Section Seekers of Perl Wisdom