You CAN do this, but there are some drawbacks. Some CPAN modules required the availability of a C compiler. Some CPAN modules have external dependencies on for instance database libraries. Some CPAN modules require build flags.
Obviously I don't know what your "applicaton stack" looks like and what the target platform(s) are, and what audience is installing your application. Basically, I'd say if you require CPAN modules and you want to deploy using say an RPM, use RPM dependencies to the RPMs from the repository where possible. Package and provide RPMs for modules that are not available by default. What you also **could** do is provide a custom compiled Perl, just for your app, with all modules you need, including C libraries where appropriate. This way you're not depending on any system provided Perl version, compiler flags, or module availability. -- Mike On Thu, Feb 3, 2011 at 8:16 PM, Mark Meyer <mme...@primexinc.com> wrote: > Hello all, > > > > > > I need to include CPAN modules as part of our custom "application stack" > installation. > > > > I was thinking that I would just include the tar gz files as part of the > application stack, then have my install scripts un-archive the modules, > then call make. > > > > is this too simple of an approach ? > > > > is anyone else faced with this same task and doing something > differently? > > > > Thank you, > > mark > > > > > > > > > > Mark Meyer > > Senior Software Engineer > > Primex Family of Companies > > 965 Wells Street > > Lake Geneva, WI 53147 > > mme...@primexinc.com > > 262-249-2384 - Direct > > 262-348-9626 - Fax > > 262-745-8840 - Cell > > > > -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
