I suggest perlbrew.
I know a 3000000+ line project with 400+ servers to deploy using perlbrew.
Never "misses" the deploy path for libs.

Also check out local::lib and Carton for some specific scenarios you might
want to support.

Regards,
gonzalo

On Jan 31, 2018 1:18 PM, "Xinhuan Zheng" <xzh...@christianbook.com> wrote:

> Dear CPAN,
>
> We are using Perl CPAN modules a lot. From time to time we need to build
> various CPAN modules for various our projects. However, we want to have a
> way to bundle them in one package so that this package can be easily
> distributed into various environments. What is best way to manage CPAN
> modules as a package? Note we are not using Active Perl. We use Unix/Linux
> platform distributed Perl.
>
> Another related question, for some reason, if a particular CPAN module we
> need requires a specific Perl version, we normally need to install local
> version of Perl, instead of using Perl from OS distribution. What is best
> way of managing two versions of Perl on same host because what would mean
> there might be two cpan paths and Perl modules to be installed could go to
> wrong Perl library path.
>
> Thanks,
>
> - xinhuan
>
>

Reply via email to