It's crazy that all the CPAN Testers tools keep configuration data in
their own way and we have tight coupling of information that must be
passed on to transports, etc.
I have released CPAN::Testers::Config to serve as the foundation for a
global CPAN Testers config file:
http://search.cpan.org/~dagolden/CPAN-Testers-Config-0.001/
It defaults to keeping data in ~/.cpantesters/config.pl but both the
directory and file can be overridden with environment variables.
The only defined key so far is global.profile, which will be the path
to a CT2.0 profile file. Nothing uses it (yet), but I plan to revise
Test::Reporter::Transport::Metabase to use it so we can stop
configuring metabase profile data separately in CPAN::Reporter and
CPANPLUS configuration. I may add a global CT 2.0 URI key as well.
That should allow CPAN::Reporter and CPANPLUS to just require
transport configuration (which could be done within module-specific
sections of CPAN::Testers::Config, too). I plan to migrate
CPAN::Reporter to use CPAN::Testers::Config sometime "soon".
I'd welcome feedback on the idea, the first draft and future
direction. If you're writing CPAN Testers tools, please consider
using this module to hold your configuration data.
-- David
