in reply to dependencies and loose coupling
You could make your installation scheme try methods (ordered from most preferred) until the correct one is found, or optionally ask, then hardwire it to the installation. Not as elegant or flexible as some design pattern acting whenever the module is used or run, but robust. ExtUtils::MakeMaker can handle that nicely.
After Compline,
Zaxo
|
|---|