<?xml version="1.0" encoding="windows-1252"?>
<node id="519176" title="Re^2: A Vision for Easy Web Application Deployment for Perl" created="2005-12-26 13:05:14" updated="2005-12-26 08:05:14">
<type id="11">
note</type>
<author id="350512">
itub</author>
<data>
<field name="doctext">
&lt;blockquote&gt;&lt;em&gt;having each application install its own version of common libraries in its own location sounds to me like a maintenance nightmare.&lt;/em&gt;&lt;/blockquote&gt;
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.

&lt;p&gt;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.</field>
<field name="root_node">
519032</field>
<field name="parent_node">
519101</field>
</data>
</node>
