Re^3: Perl application packaging

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:

What platform you're running on.
What you're deploying to (eg. servers, desktops, random users on the web)
And maybe how you want to handle CPAN packages.

Comment on Re^3: Perl application packaging

Replies are listed 'Best First'.
Re^4: Perl application packaging by bibliophile (Prior) on Jan 26, 2005 at 17:25 UTC
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]

Replies are listed 'Best First'.

Re^4: Perl application packaging
by bibliophile (Prior) on Jan 26, 2005 at 17:25 UTC

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]