On Thu, 2 Oct 2008, Aristotle Pagaltzis wrote:
* Dave Rolsky <[EMAIL PROTECTED]> [2008-10-01 17:05]:
Installation and dependency chains are an issue best solved in
the context of _applications_.
That just moves the problem, though: an that uses modules with
lots of dependencies will demand more build engineering effort.
Yes, my point is that it moves the problem to the people who are in the
best position to deal with it.
The whole "dependency problem" isn't a problem for module _authors_ like
us. If we want to depend on stuff, we install it from CPAN, develop the
new module, and release.
It's a problem if you have an application that needs to be installed in a
system with some sort of constraint. That constraint could be that the app
plays well with other apps, that modules can't be upgraded, that all code
on the system needs review by someone, etc.
The application is also the place where you can come up with multiple
solutions, like system packages, install in /opt, custom lib dir, PAR,
etc.
-dave
/*==========================
VegGuide.Org
Your guide to all that's veg
==========================*/
