#50245 closed enhancement (fixed)
Remove modules for perl 5.16, 5.18 (and 5.20?)
Reported by: | mojca (Mojca Miklavec) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | dbevans (David B. Evans), larryv (Lawrence Velázquez), danielluke (Daniel J. Luke), blair (Blair Zajac), lockhart (Thomas Lockhart), raimue (Rainer Müller), dliessi (Davide Liessi) | |
Port: | perl5 p5-graveyard |
Description (last modified by mojca (Mojca Miklavec))
Here's a list of things we have to do (please add the missing items):
empty the, r144503p5-graveyard
port; we no longer need replacements for 5.8-5.14decide whether to keep or remove support for 5.20: removeclose #48365remove, r144338, r144567perl5_16
...perl5_x
variants fromperl5
collect a list of affected ports and warn maintainersremove 5.16-5.x from, r144564, r144569perl5.branches
from ports with variants, handlesubversion-perlbindings
- 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
remove 5.16-5.x from all, r144565p5-foo
modulesfill in the, r144568p5-graveyard
port- (potential removal of
perl5.x
itself can wait)
Attachments (2)
Change History (16)
comment:1 Changed 9 years ago by mojca (Mojca Miklavec)
Description: | modified (diff) |
---|
comment:2 Changed 9 years ago by mojca (Mojca Miklavec)
Cc: | dluke@… blair@… added |
---|---|
Description: | modified (diff) |
comment:3 Changed 9 years ago by mojca (Mojca Miklavec)
Description: | modified (diff) |
---|
Changed 9 years ago by mojca (Mojca Miklavec)
Attachment: | p5-graveyard.empty.Portfile added |
---|
p5-graveyard with old subports for 5.8-5.14 removed
comment:5 follow-up: 7 Changed 9 years ago by 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.
comment:7 Changed 9 years ago by 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.
comment:8 Changed 9 years ago by mojca (Mojca Miklavec)
Description: | modified (diff) |
---|
comment:10 Changed 9 years ago by mojca (Mojca Miklavec)
Description: | modified (diff) |
---|
Variants removed from ports in r144564.
Changed 9 years ago by mojca (Mojca Miklavec)
Attachment: | remove-up-to-perl-5.22.py added |
---|
A script to remove subports p5.16 5.18 5.20
comment:11 Changed 9 years ago by mojca (Mojca Miklavec)
Description: | modified (diff) |
---|
p5.[x]-[foo]
subports removed in r144565.
Here's a list of logs to review for any (old) problems with perl modules:
comment:12 Changed 9 years ago by mojca (Mojca Miklavec)
Description: | modified (diff) |
---|
comment:13 Changed 9 years ago by mojca (Mojca Miklavec)
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:14 Changed 9 years ago by 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
These seem to have been false alarms (I didn't try to investigate the logs):
- p5-nkf
- p5-text-chasen
- p5-www-wolframalpha
Attached is the new graveyard port (with old ports removed and new ones not added yet). Lawrence, may we change it?