You could always take the approach used by, e.g., CPAN.pm - write another "module" (essentially, a .pm file with a simple wrapper around your config data) in the same directory where the module itself is going to live. That's a fairly elegant solution. It's also one that allows you to "brute-force" things when the built-in config tools aren't doing the right thing - something I've often found myself appreciating in the past. In the worst case, I could just blow away Config.pm and redo the config from scratch.

The __DATA__ section... eh. I've written self-modifying scripts in the past, and found that to be a crude and fragile approach.