That can work sometimes, but it can also put you into the dreaded “dependency hell.” I guess that a good rule of thumb for module-writers might be... if what you want to do is actually substantial and is already-done by a CPAN module, then go for it. But do try to keep the vines pruned:   don't let them just grow all over the place. Let there be a reason for each one.

A module that is reasonably self-contained, both in purpose and in implementation, will always bring smiles to your “customers.” And they are, in a certain very-real sense, your customers. The module that you are contributing to The Matrix is, in a very real sense, a “commercial product.” Try to make your customers' experience with your product a pleasant one, by anticipating their needs.