Re^3: Professional development with Perl

Compiling once the way you describe will only work if you are sure you never need to support another OS, different hardware, or a different version of Perl. These things will also change over time. You will want to upgrade your OS and suddenly find you have to recompile all of those modules by hand. Building an automated installer makes this easy, and has made it easy to deal with adding new modules.

Comment on Re^3: Professional development with Perl - how it's done?

Replies are listed 'Best First'.
Re^4: Professional development with Perl - how it's done? by Qiang (Friar) on Apr 06, 2007 at 18:43 UTC
now our app runs on Perl 5.8.7 under solaris only. I have read from "perl install" that XS modules under 5.8.* are generally compatible. but i do agree with what you said. I think i will go the route of keeping modules local to the app and also keeping a copy of unpacked modules to avoid rebuild for each app. of course a copy of module src. in case of change, Krang::Platform seems to be easy to be adopted in our environment. thank you.	[reply]
Re^5: Professional development with Perl - how it's done? by perrin (Chancellor) on Apr 06, 2007 at 19:25 UTC
If you want a sort of "best of both worlds" approach, you could build a system that can compile your modules, and then just share them around by either making tar.gz packages or using NFS. Then you can quickly recompile for a new platform, but don't need to do it on every machine. The way Krang handles this is by building binary distributions, which are just tar.gz packages with everything compiled.	[reply]