develooper Front page | perl.perl5.porters | Postings from January 2013

how to do module deprecations right on the trunk?

Thread Next
From:
Andreas Koenig
Date:
January 27, 2013 14:26
Subject:
how to do module deprecations right on the trunk?
Message ID:
878v7e4s8y.fsf@k85.linux.bogus
Among the recent deprecations of modules let me pick just one for the
sake of clarity: Module::Pluggable in commit v5.17.8-36-gc354f26.

Since this commit CoreList has not changed, but I think it should have.

This should prevent bogus fail reports from my smoker like this one
where an innocent third party (Color-Library-0.021) got a fail report
just because the new warning was introduced:

http://www.cpantesters.org/cpan/report/a82653b0-669c-11e2-b6a2-2978270fb964

Since Color-Library-0.021 declares a dependency on Module::Pluggable and
CPAN.pm promises to install dependencies and CPAN.pm consults the
Module::CoreList to identify deprecations, it would have installed it
and the warning would have been averted.

Right?

Can it be done, that deprecations get immediate reflection in core's
CoreList?

Other suggestions?

-- 
andreas

Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About