New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
modules to be removed before 5.20.0 #12727
Comments
From @rjbsThe follow Perl libraries are identified for likely removal from the perl core * Archive::Extract Candidates that were given a pass for now were: * IPC::Cmd 1: Pod::Usage and Pod::Checker would need scoped "no warnings" to avoid warning Next up: * supply patches to all upstream CPAN maintainers and request a new release |
From @rjbsSTATUS: * Archive::Extract - needs patch -- |
@rjbs - Status changed from 'new' to 'open' |
From @TuxOn Mon, 21 Jan 2013 14:58:12 -0800, Ricardo SIGNES (via RT)
* CGI ?
-- |
From @rjbsModules yet to be dealt with: * Archive::Extract - jib/archive-extract#4 -- |
From @rjbsComplicated situations: * Pod-Parser Modules patched but not released: * Archive-Extract - jib/archive-extract#4 Dists released to CPAN but not yet in blead: * Module-Pluggable Dists with deprecate.pm in core, waiting for 5.19.0: * CPANPLUS -- |
From @rjbsComplicated situations: * Pod-Parser Modules patched but not released: Dists with deprecate.pm in core, waiting for 5.19.0: * Archive-Extract -- |
From @rjbsI have removed this ticket from blocking 5.18.0, and it can be resolved shortly thereafter. -- |
From @jkeenanOn Fri Feb 08 07:32:26 2013, rjbs wrote:
rjbs: Is this ticket closable? If not, what remains to be done. Thank you very much. |
From @rjbsClosed. I'll make (or find) a new ticket to deal with sorting out the final steps of Pod::Parser. -- |
From [Unknown Contact. See original ticket]Closed. I'll make (or find) a new ticket to deal with sorting out the final steps of Pod::Parser. -- |
@rjbs - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#116491 (status was 'resolved')
Searchable as RT116491$
The text was updated successfully, but these errors were encountered: