Remove modules for perl 5.16, 5.18 (and 5.20?)

[mojca (Mojca Miklavec)]

Here's a list of things we have to do (please add the missing items):

1. empty the p5-graveyard port; we no longer need replacements for 5.8-5.14, r144503
2. decide whether to keep or remove support for 5.20: remove
3. close #48365
4. remove perl5_16 ... perl5_x variants from perl5, r144338, r144567
5. collect a list of affected ports and warn maintainers
6. remove 5.16-5.x from perl5.branches from ports with variants, handle subversion-perlbindings, r144564, r144569
   • amavisd-new
   • eperl
   • fntsample
   • fusioninventory-agent
   • git
   • git-cal
   • log2timeline
   • mod_perl2
   • openbrowser
   • ossp-uuid
   • subversion-perlbindings
   • sqlgrey
   • xraylib
   • wml
   • biblatex-biber (is there any way to simplify the last two?)
   • percona-toolkit
7. remove 5.16-5.x from all p5-foo modules, r144565
8. fill in the p5-graveyard port, r144568
9. (potential removal of perl5.x itself can wait)

[mojca (Mojca Miklavec)]

Attached is the new graveyard port (with old ports removed and new ones not added yet). Lawrence, may we change it?

[mojca (Mojca Miklavec)]

p5-graveyard with old subports for 5.8-5.14 removed

[lockhart (Thomas Lockhart)]

Cc Me!

[lockhart (Thomas Lockhart)]

I would guess this is an old and retired topic for perl5 support, but here goes anyway: why not have the recommended perl versions available in the perl5 portgroup? Something like "perl5.recommended" as a list of versions which could be assigned to perl5.branches? The simple ports I'm listed on have been completely insensitive to which perl microrelease is used and I'd guess that would continue in the future.

[raimue (Rainer Müller)]

Cc Me!

[mojca (Mojca Miklavec)]

Replying to tlockhart1976@…:

I would guess this is an old and retired topic for perl5 support, but here goes anyway: why not have the recommended perl versions available in the perl5 portgroup? Something like "perl5.recommended" as a list of versions which could be assigned to perl5.branches? The simple ports I'm listed on have been completely insensitive to which perl microrelease is used and I'd guess that would continue in the future.

These questions should be discussed in #50000.

But in short: in current implementation, even if we would put "perl5.default 5.22" and "perl5.branches 5.20 5.22" to the PortGroup, the individual ports would still need a revbump and there would be a higher chance that we would forget to revbump them. As long as individual ports need to have /opt/local/bin/perl5.22 hardcoded in their scripts, we need to rebuild all the ports.

[dliessi (Davide Liessi)]

Cc Me!

[mojca (Mojca Miklavec)]

Variants removed from ports in r144564.

[mojca (Mojca Miklavec)]

A script to remove subports p5.16 5.18 5.20

[mojca (Mojca Miklavec)]

p5.[x]-[foo] subports removed in r144565.

Here's a list of logs to review for any (old) problems with perl modules:

• ​10.6
• ​10.8
• ​10.9
• ​10.10

[mojca (Mojca Miklavec)]

• graveyard port in r144568 (some more fixes in r144566)

[mojca (Mojca Miklavec)]

On 10.6:

Building p5.22-gimp (1444 of 2734)...failure
Building p5-nkf (2113 of 2734)...failure
Building p5.22-opengl (2132 of 2734)...failure
Building p5-text-chasen (2533 of 2734)...failure
Building p5.22-text-kakasi (2541 of 2734)...failure
Building p5-www-wolframalpha (2676 of 2734)...failure

• p5.22-gimp (#50329)
• p5.22-opengl (#44417)
• p5.22-text-kakasi (#50330)

These seem to have been false alarms (I didn't try to investigate the logs):

• p5-nkf
• p5-text-chasen
• p5-www-wolframalpha