Changes between Version 2 and Version 3 of Ticket #63828


Ignore:
Timestamp:
Nov 7, 2021, 12:18:39 PM (3 years ago)
Author:
mascguy (Christopher Nielsen)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #63828

    • Property Keywords pod::parser removed
    • Property Owner changed from mojca to mascguy
    • Property Port perl5.32 perl5.34 removed

  • Ticket #63828 – Description

    v2 v3  
    1 When attempting to build this port with the default perl5 installed as `+perl5_32` or `+perl5_34`, it fails due to missing core components like `Pod::Parser`.
     1When attempting to build this port with the default perl5 installed as `+perl5_32` or `+perl5_34`, it fails due to missing core component `Pod::Parser`.
    22
    3 It's understandable that we don't yet have a complete selection of p5.xx ports for 5.32 and 5.34, since such ports are still being added. However, should our core perl5.32 and perl5.34 ports be missing things, vis-a-vis 5.30 and earlier?
     3Per the page for this component, it's been deprecated in favor of `pod-simple`:
    44
    5 To illustrate, using the example of `Pod::Parser`:
     5> NOTE: This module is considered legacy; modern Perl releases (5.18 and higher) are going to remove Pod-Parser from core and use Pod-Simple for all things POD.
    66
    7 {{{
    8 $ port contents perl5.28 | ggrep "Pod/Parser.pm"
    9   /opt/local/lib/perl5/5.28/Pod/Parser.pm
     7https://metacpan.org/pod/Pod::Parser#DESCRIPTION
    108
    11 $ port contents perl5.30 | ggrep "Pod/Parser.pm"
    12   /opt/local/lib/perl5/5.30/Pod/Parser.pm
     9So ultimately upstream will need to migrate to `pod-simple`.
    1310
    14 $ port contents perl5.32 | ggrep "Pod/Parser.pm"
    15 
    16 $ port contents perl5.34 | ggrep "Pod/Parser.pm"
    17 }}}
    18 
    19 Were these components deprecated, and/or replaced, in Perl 5.32 and beyond...?
     11In the interim, we'll note the requirement to remain with 5.30 and earlier, in a comment within the portfile for `po4a`.