What's the push to require the latest Perl?

[Daniel J. Luke]

On Jan 8, 2018, at 9:46 PM, Bill Cole <macportsusers-20171215 at billmail.scconsult.com> wrote:
> An issue with that is the fact that some amount of perl5 code in the wild (often including widely-used non-core modules) is broken with each major version. This is why upstream maintains 2 major versions at a time, releasing a new version every Spring. So if MacPorts supports just one version, it would need to be the older supported version for some months after the annual release.

We don't bend over backwards for compatibility with other ports, I don't see why we should treat perl specially in this case.

If an end-user needs to keep an older perl and associated modules around, they can either choose to not upgrade or handle it outside of macports.

-- 
Daniel J. Luke