Opened 9 years ago
Last modified 9 years ago
#50245 closed enhancement
Remove modules for perl 5.16, 5.18 (and 5.20?) — at Version 10
Reported by: | mojca (Mojca Miklavec) | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | devans@…, larryv@…, dluke@…, blair@…, tlockhart1976@…, raimue@…, 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, r144338perl5_16
...perl5_x
variants fromperl5
collect a list of affected ports and warn maintainersremove 5.16-5.x from, r144564perl5.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
p5-foo
modules - fill in the
p5-graveyard
port - (potential removal of
perl5.x
itself can wait)
Change History (12)
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
Attached is the new graveyard port (with old ports removed and new ones not added yet). Lawrence, may we change it?