http://www.perlmonks.org?node_id=519176


in reply to Re: A Vision for Easy Web Application Deployment for Perl
in thread A Vision for Easy Web Application Deployment for Perl

having each application install its own version of common libraries in its own location sounds to me like a maintenance nightmare.
Having to worry that some of the applications you have installed will break whenever you upgrade any module is also a maintenance nightmare. In the end, you should be able choose which kind of nightmare you prefer, ;-) which may depend on your situation. A user who just wants to install one blog application is not in the same situation as a webmaster maintaining several applications.

A good compromise could be to provide both options: a standard CPAN package that lets you install the dependencies separately wherever you want, and a "user-friendly" bundle that you can just unwrap and works out of the box.

  • Comment on Re^2: A Vision for Easy Web Application Deployment for Perl

Replies are listed 'Best First'.
Re^3: A Vision for Easy Web Application Deployment for Perl
by Aristotle (Chancellor) on Dec 28, 2005 at 13:34 UTC

    A good compromise could be to provide both options:

    Exactly. I wonder why noone else brought this up. Why do we always have to ask either-or questions? Often, there’s no problem pursuing both alternatives.

    Makeshifts last the longest.