Thanks to you both for your input. I don't think the modules are quite
similar enough to warrant the effort of writing a "wrapper" class
around YAML::AppConfig, but I definitely like the idea of documenting
a migration path from the deprecated to the actively maintained
module.
m.
On Thu, May 27
On Thu, May 27, 2010 at 7:12 PM, David Precious wrote:
> On Thursday 27 May 2010 16:44:58 Matt Grimm wrote:
>> The question is, how do I go about "retiring" one module on CPAN once
>> the merge is complete? I suppose the safest route might be to add a
>> big comment at the top of the retired modul
On Thursday 27 May 2010 16:44:58 Matt Grimm wrote:
> The question is, how do I go about "retiring" one module on CPAN once
> the merge is complete? I suppose the safest route might be to add a
> big comment at the top of the retired module's Pod to indicate that it
> is no longer maintained and use
Hello,
I've recently become the maintainer of two very similar CPAN modules
with the intention of merging them into a single module. The modules
are Config::YAML and YAML::AppConfig. Both can be used to manage
application configuration files in YAML, and both provide convenient
"get_*" methods to
