Re: How do you manage module deployment?

Could PAR be of any help?

It knows how to put together a working Perl-environment in a single zip file which can be deployed on another computer. If you make a "mock" script or module which uses all the modules you want to deploy, you could perhaps subvert PAR to your use.

You can tweak some settings in PAR so it does or does not include core files.

A presentation on PAR can be found here (Warning: it may not reflect the latest version of PAR, but it gives a good idea what it can do).

CountZero

"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law

Comment on Re: How do you manage module deployment? Download Code

Replies are listed 'Best First'.
Re^2: How do you manage module deployment? by hakkr (Chaplain) on Jul 13, 2005 at 09:30 UTC
pretty easy to create a zipped tarball from your source. `system ("tar -zc /sourcedir > /mytarball.tar.gz");` [download] or you can use the Archive:: cpan modules Sounds like a disk image of your perl installation might be handy as well. Or maybe you can create your own rpm's for apt or yum. Apache ant build scripts are also great for copy/moving files around Ant.	[reply] [d/l]
Re^3: How do you manage module deployment? by CountZero (Bishop) on Jul 13, 2005 at 09:38 UTC
But that is not necessarily cross-platform and may overwrite already installed modules. PAR was meant to avoid these pitfalls. Of course if you are so lucky as to have a single architecture for all your machines ... CountZero "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law	[reply]