in reply to Re: Professional development with Perl - how it's done?
in thread Professional development with Perl - how it's done?
currently, we have all the commonly used modules (such as CGI::Application and other in-house modules) in a central perl lib directory and all apps use it from there. problem may arise if a module gets upgraded with API changes and such. but i think testing may help us stay away from trouble.
to your reply, I am wondering why not unpack all needed modules locally once for your app in development and save to cvs. when deploy to the production, just cvs out. be done with it? (the only reason i can think of not doing it is unless you need to deploy to different OS). rebuilding same modules on dev,QA,production sound tedious.
or, you can keep all unpacked modules in a central location, copy to new app when needed without rebuilding it for every release.
thoughts?
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^3: Professional development with Perl - how it's done?
by perrin (Chancellor) on Apr 06, 2007 at 14:55 UTC | |
by Qiang (Friar) on Apr 06, 2007 at 18:43 UTC | |
by perrin (Chancellor) on Apr 06, 2007 at 19:25 UTC |