obsolete perls: remove perl5.8 perl5.10 perl5.12 perl5.14 from repository, update p5-graveyard

[dbevans (David B. Evans)]

At this point in time, perl5.14 and earlier versions can be considered obsolete and can be removed

• perl module support for these versions has already been removed (r130129 2014-12-27)
• no other ports depend on them
• no other ports have perl variants that refer to them

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, replaced by perl5.16 (the current default perl).

See attached patch for proposed modifications to p5-graveyard

[dbevans (David B. Evans)]

Proposed patch to obsolete perl5.14 and earlier

[mojca (Mojca Miklavec)]

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)

[mf2k (Frank Schima)]

FWIW, I think we should be moving to perl5.22 now.

[larryv (Lawrence Velázquez)]

Replying to 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 ​as usual (i.e., clearing them and adding the obsolete-1.0 portgroup)? Graveyards are meant for storing replaced subports so that subsequent updates to the main ports don’t trigger spurious build failures on the buildslaves. This doesn’t apply to the Perl ports because they’re implemented as standalone ports.

[dbevans (David B. Evans)]

OK, I agree with pretty much all the suggestions above.

I, therefore, amend my proposal to separately obsolete each of the obsolete perl ports as per the usual procedure marking them as replaced by perl5.22 as a first step in making perl5.22 the new default. If no one objects, I'll do this sooner rather than the end of the year.

At the same time, we can clear out the list of currently obsoleted perl subports from p5-graveyard so its ready for when we're ready for the next round obsoleting the p5.16 p5.18 p5.20 subports in favor of p5.22. Larry, do you want to do that?

[dbevans (David B. Evans)]

perl 5.8 5.10 5.12 5.14 obsoleted in r143273 per amended proposal. p5-graveyard left untouched.