#49940: obsolete perls: remove perl5.8 perl5.10 perl5.12 perl5.14 from repository, update p5-graveyard -------------------------------------------------+------------------------- Reporter: devans@… | Owner: devans@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: perl5.8 perl5.10 perl5.12 perl5.14 | p5-graveyard | -------------------------------------------------+------------------------- Comment (by mojca@…): My opinion: * Any tiny change in that file leads to enormous compilation times on the buildbots; if anything, I would try to remove all the `p5-foo` ports ASAP, ideally before any such change. Officially it's not been a full year since these subports have been added though, but it will soon be. (And then we'll soon need to add replacements for 5.16, 5.18 (and potentially 5.20)) * Is it too soon to auto-upgrade any `perl5.x` to `perl5.22`? * `emer` is the maintainer of 5.18, but if we get his approval, we could make a single port with a number of subports for `perl5.16` ... `perl5.22` and add all the other obsolete perl ports could live in that file (which would be a more natural place for them) -- Ticket URL: <https://trac.macports.org/ticket/49940#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X

#49940: obsolete perls: remove perl5.8 perl5.10 perl5.12 perl5.14 from repository, update p5-graveyard -------------------------------------------------+------------------------- Reporter: devans@… | Owner: devans@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: perl5.8 perl5.10 perl5.12 perl5.14 | p5-graveyard | -------------------------------------------------+------------------------- Comment (by larryv@…): Replying to [ticket:49940 devans@…]:

Unless someone can come up with a good reason not to do so, I propose to remove these ports at years end and add them to the mausoleum section of p5-graveyard declaring them obsolete

Is there some reason we can’t just obsolete the ports [https://guide.macports.org/chunked/development.practices.html#development .obsolete-portgroup as usual] (i.e., clearing them and adding the `obsolete-1.0` portgroup)? Graveyards are meant for storing replaced subports so that updating the main ports doesn’t trigger spurious build failures. This doesn’t apply to the Perl ports because they’re implemented as standalone ports. -- Ticket URL: <https://trac.macports.org/ticket/49940#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X

#49940: obsolete perls: remove perl5.8 perl5.10 perl5.12 perl5.14 from repository, update p5-graveyard -------------------------------------------------+------------------------- Reporter: devans@… | Owner: devans@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: fixed | Keywords: Port: perl5.8 perl5.10 perl5.12 perl5.14 | p5-graveyard | -------------------------------------------------+------------------------- Changes (by devans@…): * status: new => closed * resolution: => fixed Comment: perl 5.8 5.10 5.12 5.14 obsoleted in r143273 per amended proposal. p5-graveyard left untouched. -- Ticket URL: <https://trac.macports.org/ticket/49940#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X