On Tue, Apr 28, 2009 at 04:16:44PM -0700, Bill Ward wrote: > For this kind of thing I usually copy the Config.pm generated by Perl or the > CPAN::Config module -- create a MyModule::Config file that defines a hash > %MyModule::Config with all my stuff in it. The script can then just "use > MyModule::Config" and off you go.
Perhaps. But in this case I think I need to get the path to actual config files. This is an internal tool used by our developers. They can grab this "package" and install in in the normal Perl way on their machines. The package has a set of modules that manage running different binaries for them, and many of the binaries require configuration files of different formats (included in the package). In addition, it contains a wrapper script that uses the module to run the various binaries. The installer for this package also should check that they have the dependency binaries installed on their system. -- Bill Moseley. mose...@hank.org Sent from my iMutt
