On Wed, 1 Oct 2008, Aristotle Pagaltzis wrote:
* Ricardo SIGNES <[EMAIL PROTECTED]> [2008-10-01 13:45]:
I bet more CPAN authors are the same way.
Yeah. I often vacillate a great deal about adding dependencies:
• I hate making things harder to install. I’m also loathe to give
up control if I can’t trust that the delegated responsibility
is in formidably capable hands.
I really don't think _module_ authors should be worrying about this. Just
write your code and depend on whatever makes solving the particular
problem you're solving easier.
Installation and dependency chains are an issue best solved in the context
of _applications_. There are a number of ways to go about this, including
system-native packages (where they exist), Shipwright, hand-rolled
"package all the tarballs and install em", installing a separate perl or
separate lib dir per app, etc.
Different apps will find different solutions that work for them, and this
is largely dependent on the app. For example, if the app can reasonably
demand it's own server, system packages work great. If it can't, maybe
it's better off automating installing into a per-app lib dir.
And of course, an app can simply choose to forgo dependencies altogether.
-dave
/*==========================
VegGuide.Org
Your guide to all that's veg
==========================*/
