There's a ton of Config:: modules to choose from on CPAN. You should pick one that suites your tastes, it's a simple enough job that it's hard to pick badly. To me the key questions are 1) who is going to edit your config file and 2) how complicated is that configuration data.

When my answer to #1 was admins who knew Apache and the answer to #2 was Apache-style config blocks I created Config::ApacheFormat.

If you're feeling particularly ambivalent you might use Data::PhraseBook which will let you pick one format today and switch tomorrow without changing the code that uses the configs.

Another option for the undecided is Config::Auto. It may well be too clever for its own good but at least it tries hard!

Once you've picked a parser writing some glue code to populate a global %CONFIG (don't use %Config since that's what the core Config module uses and you'll probably need it someday) should be easy. If it's not, pick another module!

-sam