[Module-build-general] best way to handle module dependencies for minor features?

[Mark S. <ma...@su...>]

Hello,

I have a question about the best way to handle a module dependency
issue. I maintain Data::FormValidator. To use its basic and most common
functionality, it requires no other modules.

However, to use some it's bells-and-whistles features, it requires about
5 other modules for various things... which my have their own
dependencies. 

Recently a bug was filed against the module for "too many dependencies",
so I'm looking to possibly slim down what's required by default, while
still handle the bells-and-whistles cases gracefully, somehow.

Any recommended solutions for this kind of case? One option seems to
declare only the more critical dependencies at install time. If there is
an attempt to access a missing module, a "Module  not installed..."
message could be emitted. 

That seems like it has its own problems, though. I think my personal
tendency is error on the side of having module dependencies. Depending
on other modules sounds like "code reuse" to me, which seems like a good
thing.

	Mark

--
 . . . . . . . . . . . . . . . . . . . . . . . . . . . 
   Mark Stosberg            Principal Developer  
   ma...@su...     Summersault, LLC     
   765-939-9301 ext 202     database driven websites
 . . . . . http://www.summersault.com/ . . . . . . . .


--_----------=_1064433047325650--